Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ee40de743658c977c8ed0bdf02fb6727aa5c347f5bee287c3e3ea9174249cdd

Tx prefix hash: 4896876ad08df061d7c14bef709a3438ddaeaa7c5eeb1235e088256645bc2022
Tx public key: a91c7189aa6d550bc5ba2e7d6723c3d8c55bf3a82c437e4020e5fae855b7c911
Timestamp: 1742250248 Timestamp [UCT]: 2025-03-17 22:24:08 Age [y:d:h:m:s]: 00:248:17:31:08
Block: 1241563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175480 RingCT/type: yes/0
Extra: 01a91c7189aa6d550bc5ba2e7d6723c3d8c55bf3a82c437e4020e5fae855b7c9110211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 649d26dfa32ed403afb28226d97aba0d36f144355498c726047c82a74941a84e 0.600000000000 1728536 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": 1241573, "vin": [ { "gen": { "height": 1241563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "649d26dfa32ed403afb28226d97aba0d36f144355498c726047c82a74941a84e" } } ], "extra": [ 1, 169, 28, 113, 137, 170, 109, 85, 11, 197, 186, 46, 125, 103, 35, 195, 216, 197, 91, 243, 168, 44, 67, 126, 64, 32, 229, 250, 232, 85, 183, 201, 17, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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