Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a13a0be187ca380e5a0d369386f159b66a9b74308cce94e11076c646f71f49f

Tx prefix hash: a8f259b1d34d6235b1d624f68b73a04f3e3d5aa74a67b0490ec6834bbca83c21
Tx public key: 6996dc9e945d59258d5147c9237d76175164fe3bd362df570f86903c9be964a3
Timestamp: 1712614649 Timestamp [UCT]: 2024-04-08 22:17:29 Age [y:d:h:m:s]: 01:036:15:23:38
Block: 996300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287200 RingCT/type: yes/0
Extra: 016996dc9e945d59258d5147c9237d76175164fe3bd362df570f86903c9be964a30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34189db5038bc5d10df23e76b18b4c3202a6cae7b12633659a2361fb636dfbef 0.600000000000 1456718 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": 996310, "vin": [ { "gen": { "height": 996300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34189db5038bc5d10df23e76b18b4c3202a6cae7b12633659a2361fb636dfbef" } } ], "extra": [ 1, 105, 150, 220, 158, 148, 93, 89, 37, 141, 81, 71, 201, 35, 125, 118, 23, 81, 100, 254, 59, 211, 98, 223, 87, 15, 134, 144, 60, 155, 233, 100, 163, 2, 17, 0, 0, 0, 2, 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