Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98e4030e47fb6cdda98f9c9aaf8dc09f53948d6363e6689f7921c819e6520fa6

Tx prefix hash: 4e3da654c51f0acb4da4a1b6086a69f68ead4583f061b5c0934061ffb222f509
Tx public key: 83064fce97089695bddcc5c21517b51d604ff2a5ac134a89028c8e940113d6d3
Timestamp: 1734441590 Timestamp [UCT]: 2024-12-17 13:19:50 Age [y:d:h:m:s]: 00:022:12:56:06
Block: 1177199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16090 RingCT/type: yes/0
Extra: 0183064fce97089695bddcc5c21517b51d604ff2a5ac134a89028c8e940113d6d3021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d904334ddb25be3acb25c555ba6c5534a302b340c0f6bfccf7d95f0e23cb1dd 0.600000000000 1663564 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": 1177209, "vin": [ { "gen": { "height": 1177199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d904334ddb25be3acb25c555ba6c5534a302b340c0f6bfccf7d95f0e23cb1dd" } } ], "extra": [ 1, 131, 6, 79, 206, 151, 8, 150, 149, 189, 220, 197, 194, 21, 23, 181, 29, 96, 79, 242, 165, 172, 19, 74, 137, 2, 140, 142, 148, 1, 19, 214, 211, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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