Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5724cedeca89ed5a84eb2ef93c5257b60e6f2c4fad6b4769465030d3fe23a595

Tx prefix hash: 66bccdd3124f43f10456df5fdf08efaaf78e54db1792207e349b5939bf725ee1
Tx public key: aae83b7b41056dac0a43562ca4c400f1b2e0c7ba70fe5f4567bf991e061daae8
Timestamp: 1750488299 Timestamp [UCT]: 2025-06-21 06:44:59 Age [y:d:h:m:s]: 00:150:16:31:47
Block: 1309577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105550 RingCT/type: yes/0
Extra: 01aae83b7b41056dac0a43562ca4c400f1b2e0c7ba70fe5f4567bf991e061daae8021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 263f49c9024870318d096a5ca6a85e130c542597b62998c38f5167d849669500 0.600000000000 1797194 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": 1309587, "vin": [ { "gen": { "height": 1309577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "263f49c9024870318d096a5ca6a85e130c542597b62998c38f5167d849669500" } } ], "extra": [ 1, 170, 232, 59, 123, 65, 5, 109, 172, 10, 67, 86, 44, 164, 196, 0, 241, 178, 224, 199, 186, 112, 254, 95, 69, 103, 191, 153, 30, 6, 29, 170, 232, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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