Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ebc39f210f0e9ec44eaeae4da18192f2a9d22bee8300c04d5d68f95cd49eb23

Tx prefix hash: ce30aca5e205004b718db3690e307cca92a1d125dc9714182952c028a16f410f
Tx public key: f761173034ffb3a169f6c8a2833233aafc1a9ca785842cbe295e1fc7c68a63af
Timestamp: 1736017652 Timestamp [UCT]: 2025-01-04 19:07:32 Age [y:d:h:m:s]: 00:090:18:23:36
Block: 1190218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64647 RingCT/type: yes/0
Extra: 01f761173034ffb3a169f6c8a2833233aafc1a9ca785842cbe295e1fc7c68a63af02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b2637974f4d3ce496613dbd5c7c2e2c4f1c736ae1e618d598ce4a29809e6766 0.600000000000 1676733 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": 1190228, "vin": [ { "gen": { "height": 1190218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b2637974f4d3ce496613dbd5c7c2e2c4f1c736ae1e618d598ce4a29809e6766" } } ], "extra": [ 1, 247, 97, 23, 48, 52, 255, 179, 161, 105, 246, 200, 162, 131, 50, 51, 170, 252, 26, 156, 167, 133, 132, 44, 190, 41, 94, 31, 199, 198, 138, 99, 175, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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