Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf0a4b64f6fa1773ef7488c79d59b41a7a1ca796ff9b5223f5ad14f1a3a3e1a

Tx prefix hash: a59f85ff47cbcad3fef7d0c53a3349adb3c68b6a0c479acd993ef2c85d958239
Tx public key: ee7c3ae9af6416802a50336c51c7dfc6e03ffaaf5b32cd82d7caa70ade29e3bd
Timestamp: 1733518221 Timestamp [UCT]: 2024-12-06 20:50:21 Age [y:d:h:m:s]: 00:117:00:56:07
Block: 1169525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83432 RingCT/type: yes/0
Extra: 01ee7c3ae9af6416802a50336c51c7dfc6e03ffaaf5b32cd82d7caa70ade29e3bd0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1bbbaa7ab0793557e5b31543c0dab02e314fe20c91a82f9b1aa323c3e16f15a 0.600000000000 1655244 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": 1169535, "vin": [ { "gen": { "height": 1169525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1bbbaa7ab0793557e5b31543c0dab02e314fe20c91a82f9b1aa323c3e16f15a" } } ], "extra": [ 1, 238, 124, 58, 233, 175, 100, 22, 128, 42, 80, 51, 108, 81, 199, 223, 198, 224, 63, 250, 175, 91, 50, 205, 130, 215, 202, 167, 10, 222, 41, 227, 189, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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