Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e04c77e681b2cbe397495638aeb53eb6f9d52720930951ce2cbb68050dbb943

Tx prefix hash: ccc7049c74314e7fc8b01441fe42ab9f80be6dbf3829fb59999e6e877ec214c2
Tx public key: 8a992dee26f61f40b65f2cfabbde9a1aa970c32d3cf2ff77a3e8f875dc89cecc
Timestamp: 1745295201 Timestamp [UCT]: 2025-04-22 04:13:21 Age [y:d:h:m:s]: 00:203:03:57:30
Block: 1266741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142924 RingCT/type: yes/0
Extra: 018a992dee26f61f40b65f2cfabbde9a1aa970c32d3cf2ff77a3e8f875dc89cecc021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e8c8df4129c972bc166ca216f64ced9eda32030715baa99864cbeb904fc09fc 0.600000000000 1753962 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": 1266751, "vin": [ { "gen": { "height": 1266741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e8c8df4129c972bc166ca216f64ced9eda32030715baa99864cbeb904fc09fc" } } ], "extra": [ 1, 138, 153, 45, 238, 38, 246, 31, 64, 182, 95, 44, 250, 187, 222, 154, 26, 169, 112, 195, 45, 60, 242, 255, 119, 163, 232, 248, 117, 220, 137, 206, 204, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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