Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a2bce8a96ff3cc37604958de223e711daf070ab831b7329ffc64d47f8630e03

Tx prefix hash: d1ac6a6db2391e9e225cdd8777cfe7a5217a15efcf03bde1e0cb70fcf51991de
Tx public key: 1f6ce652840aeb975ad51d08145a749e20a54ab5f1fa9394dea7fd22a3697c42
Timestamp: 1712310972 Timestamp [UCT]: 2024-04-05 09:56:12 Age [y:d:h:m:s]: 00:364:04:24:03
Block: 993780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260403 RingCT/type: yes/0
Extra: 011f6ce652840aeb975ad51d08145a749e20a54ab5f1fa9394dea7fd22a3697c420211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf070e974dac92b452dfbf7c5e88cb80f77496eaa0f456fe4e1061ea29478ce4 0.600000000000 1454168 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": 993790, "vin": [ { "gen": { "height": 993780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf070e974dac92b452dfbf7c5e88cb80f77496eaa0f456fe4e1061ea29478ce4" } } ], "extra": [ 1, 31, 108, 230, 82, 132, 10, 235, 151, 90, 213, 29, 8, 20, 90, 116, 158, 32, 165, 74, 181, 241, 250, 147, 148, 222, 167, 253, 34, 163, 105, 124, 66, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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