Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 317d12283a4addaca2e2e57d5178a0b2ee9beb11f7af5b0293422aebdd75f863

Tx prefix hash: 504b8fa4c5020b65749f6da1c738ca7fde93d3cd0defda312b78a71592333b21
Tx public key: 6a11e16206d4ec76d4a693001f1253cf53c8e31d08e21628b9b1fb2493ebe7e5
Timestamp: 1627609534 Timestamp [UCT]: 2021-07-30 01:45:34 Age [y:d:h:m:s]: 03:150:20:57:56
Block: 303544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 880337 RingCT/type: yes/0
Extra: 016a11e16206d4ec76d4a693001f1253cf53c8e31d08e21628b9b1fb2493ebe7e5021100000011e084ab86000000000000000000

1 output(s) for total of 60.566601623000 dcy

stealth address amount amount idx
00: 1faf2c04a95a66837f2c9312b3d952b52c0235acc5d38a5c692d2954f7dc35f2 60.566601623000 633527 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": 303554, "vin": [ { "gen": { "height": 303544 } } ], "vout": [ { "amount": 60566601623, "target": { "key": "1faf2c04a95a66837f2c9312b3d952b52c0235acc5d38a5c692d2954f7dc35f2" } } ], "extra": [ 1, 106, 17, 225, 98, 6, 212, 236, 118, 212, 166, 147, 0, 31, 18, 83, 207, 83, 200, 227, 29, 8, 226, 22, 40, 185, 177, 251, 36, 147, 235, 231, 229, 2, 17, 0, 0, 0, 17, 224, 132, 171, 134, 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