Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5e6df8d0b4ae68790b837f1e33d999e54f550090261f3ef6c8669811b33346

Tx prefix hash: 11f029662f346c381f7fa61816a45a788de8cd0a40bd970b6c4dd9de4b8e2f8f
Tx public key: 31aa60cf23d71e6cd61474f677db3d41688d487b8ca06d966b5fe4bce9e1234c
Timestamp: 1699066742 Timestamp [UCT]: 2023-11-04 02:59:02 Age [y:d:h:m:s]: 01:156:09:06:07
Block: 884213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372749 RingCT/type: yes/0
Extra: 0131aa60cf23d71e6cd61474f677db3d41688d487b8ca06d966b5fe4bce9e1234c021100000004faf35c9c000000000000000000

1 output(s) for total of 0.721498252000 dcy

stealth address amount amount idx
00: 84b541147f8130cfeaca55e85cc3f75e892c350e3f8a6bdc64849941050219b5 0.721498252000 1339950 of 0

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": 884223, "vin": [ { "gen": { "height": 884213 } } ], "vout": [ { "amount": 721498252, "target": { "key": "84b541147f8130cfeaca55e85cc3f75e892c350e3f8a6bdc64849941050219b5" } } ], "extra": [ 1, 49, 170, 96, 207, 35, 215, 30, 108, 214, 20, 116, 246, 119, 219, 61, 65, 104, 141, 72, 123, 140, 160, 109, 150, 107, 95, 228, 188, 233, 225, 35, 76, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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