Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9111af2f352e538a7426e9037cdbc0f4017c5c7ed6b7c3d7ebf64eb94cb7227b

Tx prefix hash: c7a5aaf239c2a3d16457ec89b86221d338d09b218316d324057e9a92a6217dcf
Tx public key: 8c5e50d6e32c9e1952e91d2354c0b2e7d0ad419fb284d3d74d884677b31f9fe2
Timestamp: 1732649822 Timestamp [UCT]: 2024-11-26 19:37:02 Age [y:d:h:m:s]: 00:153:14:21:49
Block: 1162328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109616 RingCT/type: yes/0
Extra: 018c5e50d6e32c9e1952e91d2354c0b2e7d0ad419fb284d3d74d884677b31f9fe20211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1c7a231e829c897d52bc3843196173c0ffe47e767a44e0951df33977d247cf4 0.600000000000 1647983 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": 1162338, "vin": [ { "gen": { "height": 1162328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1c7a231e829c897d52bc3843196173c0ffe47e767a44e0951df33977d247cf4" } } ], "extra": [ 1, 140, 94, 80, 214, 227, 44, 158, 25, 82, 233, 29, 35, 84, 192, 178, 231, 208, 173, 65, 159, 178, 132, 211, 215, 77, 136, 70, 119, 179, 31, 159, 226, 2, 17, 0, 0, 0, 8, 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