Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0527bd762eeb9b70dde0f841ab7e4d9b2420c36844985a4f4acc4890643c6d0d

Tx prefix hash: b291cf41b1b747c27f0115cfff1ea08bf3ba5784dfcb78ab1abfdbe41e6bdf46
Tx public key: 2914237ffcde23613ae91ab52c17ce491b11cedf80d6968e3b4d6c079518fb96
Timestamp: 1713813357 Timestamp [UCT]: 2024-04-22 19:15:57 Age [y:d:h:m:s]: 00:253:17:41:00
Block: 1006267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181622 RingCT/type: yes/0
Extra: 012914237ffcde23613ae91ab52c17ce491b11cedf80d6968e3b4d6c079518fb9602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5e432fcfb015f73b179a9741ce60b8e99ae7b753ebf2423d4e5a8b931965e32 0.600000000000 1467231 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": 1006277, "vin": [ { "gen": { "height": 1006267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5e432fcfb015f73b179a9741ce60b8e99ae7b753ebf2423d4e5a8b931965e32" } } ], "extra": [ 1, 41, 20, 35, 127, 252, 222, 35, 97, 58, 233, 26, 181, 44, 23, 206, 73, 27, 17, 206, 223, 128, 214, 150, 142, 59, 77, 108, 7, 149, 24, 251, 150, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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