Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be4c7a27b0010fe21fa18564160380af4d24c7dc2c0552e2b2bf1349261e3b4

Tx prefix hash: 6d7089e8056a13fddbea1f975f21aa33299a34d75835609d6c4a8c1ee02f895a
Tx public key: e5f14d2129cb38149bb64cda1aa2c76bf1838c88f50278dbe858f3d69fa68d7e
Timestamp: 1715382194 Timestamp [UCT]: 2024-05-10 23:03:14 Age [y:d:h:m:s]: 00:310:13:37:47
Block: 1019285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221989 RingCT/type: yes/0
Extra: 01e5f14d2129cb38149bb64cda1aa2c76bf1838c88f50278dbe858f3d69fa68d7e02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af93dc073e43799c75fd3aab1d1003c0818930103c147be527eabedf9d069381 0.600000000000 1483214 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": 1019295, "vin": [ { "gen": { "height": 1019285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af93dc073e43799c75fd3aab1d1003c0818930103c147be527eabedf9d069381" } } ], "extra": [ 1, 229, 241, 77, 33, 41, 203, 56, 20, 155, 182, 76, 218, 26, 162, 199, 107, 241, 131, 140, 136, 245, 2, 120, 219, 232, 88, 243, 214, 159, 166, 141, 126, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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