Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24d65a871379185bbe91e0910a9fee0dc2d042ba51cd6f66948c02f09a18797d

Tx prefix hash: 092e47ddf698e487342c19d0ba2094fb6358c4a33b603f4b8df99b29a1b3f522
Tx public key: d31719931e90c45e31ceefb2f8e7f6f9da8d7d053a60888bc74403b848c76675
Timestamp: 1733479149 Timestamp [UCT]: 2024-12-06 09:59:09 Age [y:d:h:m:s]: 00:335:17:08:26
Block: 1169209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237437 RingCT/type: yes/0
Extra: 01d31719931e90c45e31ceefb2f8e7f6f9da8d7d053a60888bc74403b848c766750211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3975dc9efd07c7123eef9ba1971f70e7d4f7bf194fe96daed10072c7884d319 0.600000000000 1654924 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": 1169219, "vin": [ { "gen": { "height": 1169209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3975dc9efd07c7123eef9ba1971f70e7d4f7bf194fe96daed10072c7884d319" } } ], "extra": [ 1, 211, 23, 25, 147, 30, 144, 196, 94, 49, 206, 239, 178, 248, 231, 246, 249, 218, 141, 125, 5, 58, 96, 136, 139, 199, 68, 3, 184, 72, 199, 102, 117, 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