Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34c479f08d4a7588c3a6a6cdc5b30b7ad7dbf6298c3b15fd0d78f1738efcae6a

Tx prefix hash: 05b382e2788cd8fea81d9cb4b54c178546e6ac47c49e07135182c6293de158b6
Tx public key: 418e4df7150d426e18600b37ce474ba086e34368247d7524b9dbc41bc9a39a91
Timestamp: 1709125486 Timestamp [UCT]: 2024-02-28 13:04:46 Age [y:d:h:m:s]: 01:040:03:10:47
Block: 967410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289689 RingCT/type: yes/0
Extra: 01418e4df7150d426e18600b37ce474ba086e34368247d7524b9dbc41bc9a39a9102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39da8bb80a7eb1bda84d39c4cfee96b9e0ffb9463e28add79125e542a09afcfc 0.600000000000 1427189 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": 967420, "vin": [ { "gen": { "height": 967410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39da8bb80a7eb1bda84d39c4cfee96b9e0ffb9463e28add79125e542a09afcfc" } } ], "extra": [ 1, 65, 142, 77, 247, 21, 13, 66, 110, 24, 96, 11, 55, 206, 71, 75, 160, 134, 227, 67, 104, 36, 125, 117, 36, 185, 219, 196, 27, 201, 163, 154, 145, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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