Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a9da547982999014ed8a7323fb7ac579c1a4d8f926a191ee12ece4bac8d4b65

Tx prefix hash: baec5cc6a774154ea28a829f8bff24e9379769841f0fac410e73cf962ecfb483
Tx public key: 499cb0313ff5ce9d4c3b50fdb6e92bb28b2337cfb35c0dbe846740fa9db3bd6a
Timestamp: 1728810803 Timestamp [UCT]: 2024-10-13 09:13:23 Age [y:d:h:m:s]: 00:070:20:43:56
Block: 1130607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50664 RingCT/type: yes/0
Extra: 01499cb0313ff5ce9d4c3b50fdb6e92bb28b2337cfb35c0dbe846740fa9db3bd6a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c98d78689d17a97f5bc84076f2af40056f503bc418012c172f81a47fd395de7 0.600000000000 1613484 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": 1130617, "vin": [ { "gen": { "height": 1130607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c98d78689d17a97f5bc84076f2af40056f503bc418012c172f81a47fd395de7" } } ], "extra": [ 1, 73, 156, 176, 49, 63, 245, 206, 157, 76, 59, 80, 253, 182, 233, 43, 178, 139, 35, 55, 207, 179, 92, 13, 190, 132, 103, 64, 250, 157, 179, 189, 106, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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