Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93ac05d5b8a51f6e573681423ef7aad156fbf2a7b8ce837dbf12c98ba284b422

Tx prefix hash: e964831717123ceede197e9ba602c6df3aecc9f376df4fa3637a6bd880e4d61f
Tx public key: 97ac7acc60a30fa8e585b308368571b6f12118f6f98f309206083c77a3f30d8b
Timestamp: 1715381305 Timestamp [UCT]: 2024-05-10 22:48:25 Age [y:d:h:m:s]: 00:358:05:48:08
Block: 1019280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256068 RingCT/type: yes/0
Extra: 0197ac7acc60a30fa8e585b308368571b6f12118f6f98f309206083c77a3f30d8b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab4f35df9b93146bc47c227db25249f0a959c23fb96d154443524fc8aa9c9172 0.600000000000 1483205 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": 1019290, "vin": [ { "gen": { "height": 1019280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab4f35df9b93146bc47c227db25249f0a959c23fb96d154443524fc8aa9c9172" } } ], "extra": [ 1, 151, 172, 122, 204, 96, 163, 15, 168, 229, 133, 179, 8, 54, 133, 113, 182, 241, 33, 24, 246, 249, 143, 48, 146, 6, 8, 60, 119, 163, 243, 13, 139, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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