Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d46d304e2559433ce34e0f8c47770bb95ab9f048edb591dd4e7188adddca9c4e

Tx prefix hash: 7a9170c51efeff3eff2f0a85902729e88ddfc25aa9c6ffa00b47413c9ffa8e5e
Tx public key: 9ba6b7ed38e9f007d4979c239080cc4f46ff0c553f871db85a231f0c4da00665
Timestamp: 1726155080 Timestamp [UCT]: 2024-09-12 15:31:20 Age [y:d:h:m:s]: 00:217:17:49:27
Block: 1108577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155469 RingCT/type: yes/0
Extra: 019ba6b7ed38e9f007d4979c239080cc4f46ff0c553f871db85a231f0c4da0066502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e0055c6a8fa73a3b105385aa6afe15d65f1afdc293f9b2a3902fcd0fa42156c 0.600000000000 1586524 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": 1108587, "vin": [ { "gen": { "height": 1108577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e0055c6a8fa73a3b105385aa6afe15d65f1afdc293f9b2a3902fcd0fa42156c" } } ], "extra": [ 1, 155, 166, 183, 237, 56, 233, 240, 7, 212, 151, 156, 35, 144, 128, 204, 79, 70, 255, 12, 85, 63, 135, 29, 184, 90, 35, 31, 12, 77, 160, 6, 101, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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