Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 548e2f336dbc909cc52d425c8bd4b3ff7b03eb5e3471e43821d28fb78517e04d

Tx prefix hash: d547acef2ec854416f748ff38524b7586c9e9986553d2338fd1e30b889eeda70
Tx public key: bea38720dac695614c8e3aa6ba56ead94f7c83b6bba1fa21d225e01ec6449a7d
Timestamp: 1723926418 Timestamp [UCT]: 2024-08-17 20:26:58 Age [y:d:h:m:s]: 01:085:04:06:31
Block: 1090111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319334 RingCT/type: yes/0
Extra: 01bea38720dac695614c8e3aa6ba56ead94f7c83b6bba1fa21d225e01ec6449a7d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0f3e4a7671c440dde15de34aa14c3c829446cdab74171d4713f11f6be1a9078 0.600000000000 1564734 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": 1090121, "vin": [ { "gen": { "height": 1090111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0f3e4a7671c440dde15de34aa14c3c829446cdab74171d4713f11f6be1a9078" } } ], "extra": [ 1, 190, 163, 135, 32, 218, 198, 149, 97, 76, 142, 58, 166, 186, 86, 234, 217, 79, 124, 131, 182, 187, 161, 250, 33, 210, 37, 224, 30, 198, 68, 154, 125, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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