Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d9970d5358024ff6bd024c4f98ecfea31ee831d2a01a9e90471fc8013df600a

Tx prefix hash: 6de2e61a8dbd14a991affc5de0093d78fad20ad6ff72bfeadfd5b05e60ff7f15
Tx public key: 306319be59af04b4059104ec0e005cdd68b430df803bd4d12071e5aac671cf8a
Timestamp: 1707894079 Timestamp [UCT]: 2024-02-14 07:01:19 Age [y:d:h:m:s]: 01:087:01:38:12
Block: 957184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323294 RingCT/type: yes/0
Extra: 01306319be59af04b4059104ec0e005cdd68b430df803bd4d12071e5aac671cf8a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cc6b1f9e32758f42b5bb0eee8b73196ee062f0455b7765e57e6e20d18862e44 0.600000000000 1416500 of 15

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": 957194, "vin": [ { "gen": { "height": 957184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cc6b1f9e32758f42b5bb0eee8b73196ee062f0455b7765e57e6e20d18862e44" } } ], "extra": [ 1, 48, 99, 25, 190, 89, 175, 4, 180, 5, 145, 4, 236, 14, 0, 92, 221, 104, 180, 48, 223, 128, 59, 212, 209, 32, 113, 229, 170, 198, 113, 207, 138, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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