Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a20e0e8541386c2f7a3703137c7bb848ee52c5935b673b10b9ddbd931ae11885

Tx prefix hash: 222dfdec03878c4f1034dc5c4ef190c8c95e55fcfab0b89ffa00498f62d025d2
Tx public key: f269adef236630b28c108bc031ae78c04c2531492a45f676edc74b0a82144365
Timestamp: 1577048565 Timestamp [UCT]: 2019-12-22 21:02:45 Age [y:d:h:m:s]: 05:155:16:08:25
Block: 29743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1260897 RingCT/type: yes/0
Extra: 01f269adef236630b28c108bc031ae78c04c2531492a45f676edc74b0a8214436502110000002d8a2ee0d9000000000000000000

1 output(s) for total of 489.158896679000 dcy

stealth address amount amount idx
00: 28f030f6d71ec72a658d8a94457359ea902a0a7414a2c70ab132a2e6ff98d71b 489.158896679000 48987 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": 29753, "vin": [ { "gen": { "height": 29743 } } ], "vout": [ { "amount": 489158896679, "target": { "key": "28f030f6d71ec72a658d8a94457359ea902a0a7414a2c70ab132a2e6ff98d71b" } } ], "extra": [ 1, 242, 105, 173, 239, 35, 102, 48, 178, 140, 16, 139, 192, 49, 174, 120, 192, 76, 37, 49, 73, 42, 69, 246, 118, 237, 199, 75, 10, 130, 20, 67, 101, 2, 17, 0, 0, 0, 45, 138, 46, 224, 217, 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