Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd34c484b7ef0b7edfe1160440f6318734e89e5a719d59372446976ac591baa0

Tx prefix hash: 42775957c0e0b8674f1cb18b2e8c979f79b544e74553b995eab721040c823127
Tx public key: 512a39aac219935771b8511f6f5acb51df9e9f29190c28ede226c9f1f196cc97
Timestamp: 1712346780 Timestamp [UCT]: 2024-04-05 19:53:00 Age [y:d:h:m:s]: 01:180:23:05:10
Block: 994074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387986 RingCT/type: yes/0
Extra: 01512a39aac219935771b8511f6f5acb51df9e9f29190c28ede226c9f1f196cc9702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8171470003d1a1dc0b171da647e482cec84d53d81a2debe0d48e7d145df30250 0.600000000000 1454472 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": 994084, "vin": [ { "gen": { "height": 994074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8171470003d1a1dc0b171da647e482cec84d53d81a2debe0d48e7d145df30250" } } ], "extra": [ 1, 81, 42, 57, 170, 194, 25, 147, 87, 113, 184, 81, 31, 111, 90, 203, 81, 223, 158, 159, 41, 25, 12, 40, 237, 226, 38, 201, 241, 241, 150, 204, 151, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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