Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e39ae33334c5e1180796fecfc67a8092daaad15d4cf6b4fce5d6867e8cc7e34

Tx prefix hash: e799807cb701c80fd3e464044b34495ef8e44fd7a1d68f13d43268801f284e0c
Tx public key: a660493f2b1bebb83233ca2d930f0ee1618d6f51c6b94cf0ab94190bed228e8b
Timestamp: 1719045908 Timestamp [UCT]: 2024-06-22 08:45:08 Age [y:d:h:m:s]: 01:195:02:53:36
Block: 1049632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398095 RingCT/type: yes/0
Extra: 01a660493f2b1bebb83233ca2d930f0ee1618d6f51c6b94cf0ab94190bed228e8b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d634811772324aaf2027c2011ed0d845b03e08a7b98ea2ce468a45c20df90eb4 0.600000000000 1519733 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": 1049642, "vin": [ { "gen": { "height": 1049632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d634811772324aaf2027c2011ed0d845b03e08a7b98ea2ce468a45c20df90eb4" } } ], "extra": [ 1, 166, 96, 73, 63, 43, 27, 235, 184, 50, 51, 202, 45, 147, 15, 14, 225, 97, 141, 111, 81, 198, 185, 76, 240, 171, 148, 25, 11, 237, 34, 142, 139, 2, 17, 0, 0, 0, 1, 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