Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0f17cdcfb0f4c2aee365c9d42b9ab95a3eec27f926bcf4fba411a1363f7d215

Tx prefix hash: cea32254fa220dc85a8c555db3a21dcdf2354c62dd5d327efe5bb97d5baa8b94
Tx public key: d08d130b7b167d61c95f7afce804f8dcebaf54e42cc47a57dbabc9854ef71bce
Timestamp: 1703902462 Timestamp [UCT]: 2023-12-30 02:14:22 Age [y:d:h:m:s]: 01:128:23:43:38
Block: 924099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353319 RingCT/type: yes/0
Extra: 01d08d130b7b167d61c95f7afce804f8dcebaf54e42cc47a57dbabc9854ef71bce0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf486ffe5580643e6b743b04173c14ed0445f6ea0fd5b3fad5f4225240cc64ea 0.600000000000 1381841 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": 924109, "vin": [ { "gen": { "height": 924099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf486ffe5580643e6b743b04173c14ed0445f6ea0fd5b3fad5f4225240cc64ea" } } ], "extra": [ 1, 208, 141, 19, 11, 123, 22, 125, 97, 201, 95, 122, 252, 232, 4, 248, 220, 235, 175, 84, 228, 44, 196, 122, 87, 219, 171, 201, 133, 78, 247, 27, 206, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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