Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3dcb1e26251b197b8421d26497aaa413377e095a8d44766b477491108af56bc

Tx prefix hash: 1f8933cf22de8e9b1d54fce51c9ac226bddf4af7dbf39d4baef71f64afae2c7e
Tx public key: ce899114af277db1fdd155d6cd7e01f69fed3f957ad98af8d804a9e68ca9a64d
Timestamp: 1708785826 Timestamp [UCT]: 2024-02-24 14:43:46 Age [y:d:h:m:s]: 01:046:11:15:21
Block: 964588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294228 RingCT/type: yes/0
Extra: 01ce899114af277db1fdd155d6cd7e01f69fed3f957ad98af8d804a9e68ca9a64d02110000000279bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55d12e615e70f488b0b23cb1b310b1b66e36b3c25806b5d5b104a3e529707560 0.600000000000 1424329 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": 964598, "vin": [ { "gen": { "height": 964588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55d12e615e70f488b0b23cb1b310b1b66e36b3c25806b5d5b104a3e529707560" } } ], "extra": [ 1, 206, 137, 145, 20, 175, 39, 125, 177, 253, 209, 85, 214, 205, 126, 1, 246, 159, 237, 63, 149, 122, 217, 138, 248, 216, 4, 169, 230, 140, 169, 166, 77, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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