Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dad87fbd96e75d014399baa2f48daccca4f2ba2bce41ee4409725b64a206e30

Tx prefix hash: c6b7e0c785cb7a551bc79beaf35eaeabfbd063a287991db0b027074fd9ba7e6b
Tx public key: 9a5e61ddb1e53e9cb4108d97e1d4af29b7f004b8e8597b22c62b682a0f13d3a7
Timestamp: 1700907371 Timestamp [UCT]: 2023-11-25 10:16:11 Age [y:d:h:m:s]: 02:059:08:30:14
Block: 899270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 562129 RingCT/type: yes/0
Extra: 019a5e61ddb1e53e9cb4108d97e1d4af29b7f004b8e8597b22c62b682a0f13d3a702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.643198717000 dcy

stealth address amount amount idx
00: ce095f151be4ddb0a320868a00ece589a31047d20f927240b199772419c174f6 0.643198717000 1355717 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": 899280, "vin": [ { "gen": { "height": 899270 } } ], "vout": [ { "amount": 643198717, "target": { "key": "ce095f151be4ddb0a320868a00ece589a31047d20f927240b199772419c174f6" } } ], "extra": [ 1, 154, 94, 97, 221, 177, 229, 62, 156, 180, 16, 141, 151, 225, 212, 175, 41, 183, 240, 4, 184, 232, 89, 123, 34, 198, 43, 104, 42, 15, 19, 211, 167, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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