Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d05bb09148c0fea21def8fe2af8ddcafd4bd1cc9d644e44fbce40dc6721fcdf

Tx prefix hash: d2558fced0d1be0e7ca43d8f046d1bf5a9feb35aa754f78c8ed7813e32fffdc0
Tx public key: 12bac1878a3635f66717805956c37d1143efadfb8b360d846f35c751134a6171
Timestamp: 1746250097 Timestamp [UCT]: 2025-05-03 05:28:17 Age [y:d:h:m:s]: 00:201:20:10:26
Block: 1274663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141955 RingCT/type: yes/0
Extra: 0112bac1878a3635f66717805956c37d1143efadfb8b360d846f35c751134a61710211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f557a19ca1b2139d871e2d3a3e9b5d9a202c7c107cc4bf76be182210c275d9 0.600000000000 1761960 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": 1274673, "vin": [ { "gen": { "height": 1274663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f557a19ca1b2139d871e2d3a3e9b5d9a202c7c107cc4bf76be182210c275d9" } } ], "extra": [ 1, 18, 186, 193, 135, 138, 54, 53, 246, 103, 23, 128, 89, 86, 195, 125, 17, 67, 239, 173, 251, 139, 54, 13, 132, 111, 53, 199, 81, 19, 74, 97, 113, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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