Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e49be0969540c988d80ac77c30e625893cc618f350dbea4a9408216b13175202

Tx prefix hash: 61d1d5eeaad852f6750c6a16e27af5737d26541c13b40e1727d33c60ed2ee27b
Tx public key: 0a7066b47e2e466d6d8f24e83398c00f4d2b4e44966c53f0a6febff0750462d3
Timestamp: 1725337329 Timestamp [UCT]: 2024-09-03 04:22:09 Age [y:d:h:m:s]: 00:209:23:20:06
Block: 1101800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149910 RingCT/type: yes/0
Extra: 010a7066b47e2e466d6d8f24e83398c00f4d2b4e44966c53f0a6febff0750462d3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b45c74b32792980f46adc394fb2f8707a2a5412bc3006275be01cc0be9996e5a 0.600000000000 1577991 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": 1101810, "vin": [ { "gen": { "height": 1101800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b45c74b32792980f46adc394fb2f8707a2a5412bc3006275be01cc0be9996e5a" } } ], "extra": [ 1, 10, 112, 102, 180, 126, 46, 70, 109, 109, 143, 36, 232, 51, 152, 192, 15, 77, 43, 78, 68, 150, 108, 83, 240, 166, 254, 191, 240, 117, 4, 98, 211, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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