Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01b2ae9717680d6a0d80d0f6669caf775cb3909b18625affc726d18f09cabe5

Tx prefix hash: 24417ac4b542cfdfe50b5cdda2ea31af32bdcc1634060e7a02428fc838bf4eec
Tx public key: 25a056a75dc030078eb65a1615a12946052e0eaefe8b71f059a1c562f4218ecb
Timestamp: 1727997405 Timestamp [UCT]: 2024-10-03 23:16:45 Age [y:d:h:m:s]: 00:110:10:38:08
Block: 1123858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78915 RingCT/type: yes/0
Extra: 0125a056a75dc030078eb65a1615a12946052e0eaefe8b71f059a1c562f4218ecb02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb08bd92e37b5b8fac95a389197a13af0ebf3b5d160bc0e5ac57f4258582e384 0.600000000000 1606397 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": 1123868, "vin": [ { "gen": { "height": 1123858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb08bd92e37b5b8fac95a389197a13af0ebf3b5d160bc0e5ac57f4258582e384" } } ], "extra": [ 1, 37, 160, 86, 167, 93, 192, 48, 7, 142, 182, 90, 22, 21, 161, 41, 70, 5, 46, 14, 174, 254, 139, 113, 240, 89, 161, 197, 98, 244, 33, 142, 203, 2, 17, 0, 0, 0, 11, 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