Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb3ab149c6c56c924e3a870195fc733feef269c214ac6ade5e2c60f05aa55507

Tx prefix hash: 34e7ce9999ed2dc669d71a14ada6c18185aa95853e78cb7ccc85fb3fc1fb6ea6
Tx public key: 0d115e1d20226b0464c1bc958cf29ea2ca82c663ce4eafdc9b04eb680709e974
Timestamp: 1577763010 Timestamp [UCT]: 2019-12-31 03:30:10 Age [y:d:h:m:s]: 05:038:01:13:37
Block: 35446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176960 RingCT/type: yes/0
Extra: 010d115e1d20226b0464c1bc958cf29ea2ca82c663ce4eafdc9b04eb680709e9740211000000128a2ee0d9000000000000000000

1 output(s) for total of 468.331686061000 dcy

stealth address amount amount idx
00: 7e4c7e391f72ddbd717dab08956ea7f5c43d4b745c0714c6de5ac2187022abf7 468.331686061000 59780 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": 35456, "vin": [ { "gen": { "height": 35446 } } ], "vout": [ { "amount": 468331686061, "target": { "key": "7e4c7e391f72ddbd717dab08956ea7f5c43d4b745c0714c6de5ac2187022abf7" } } ], "extra": [ 1, 13, 17, 94, 29, 32, 34, 107, 4, 100, 193, 188, 149, 140, 242, 158, 162, 202, 130, 198, 99, 206, 78, 175, 220, 155, 4, 235, 104, 7, 9, 233, 116, 2, 17, 0, 0, 0, 18, 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