Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5358e49fc13589279f2c0365e315842eff3511ae028968c27449219defde8232

Tx prefix hash: 63495ef81ae623dea679327f1902ad2a0d8c3fcf1389d936874a9e981e3fd6ae
Tx public key: 1fb8fae59d5ce54cf7680dc81329956756b1edad126a5fd3513ed33d7d5a40b9
Timestamp: 1700907055 Timestamp [UCT]: 2023-11-25 10:10:55 Age [y:d:h:m:s]: 01:359:10:29:53
Block: 899266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515783 RingCT/type: yes/0
Extra: 011fb8fae59d5ce54cf7680dc81329956756b1edad126a5fd3513ed33d7d5a40b9021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.643218347000 dcy

stealth address amount amount idx
00: e327bc954b0c46c836489a6c453135c04e8419c160ff1ece9bd4344b3ab58e95 0.643218347000 1355713 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 899276, "vin": [ { "gen": { "height": 899266 } } ], "vout": [ { "amount": 643218347, "target": { "key": "e327bc954b0c46c836489a6c453135c04e8419c160ff1ece9bd4344b3ab58e95" } } ], "extra": [ 1, 31, 184, 250, 229, 157, 92, 229, 76, 247, 104, 13, 200, 19, 41, 149, 103, 86, 177, 237, 173, 18, 106, 95, 211, 81, 62, 211, 61, 125, 90, 64, 185, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8