Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9043fcb46cd0904f76a7397464b6c1372886bc8d92d9a198a9213e3e6cff35ea

Tx prefix hash: 81404f30ced93cae14f7443d5a7b08f786a36e1d8c482c5e889ef60f8daecde8
Tx public key: a7d32995488cf01ba81e7b948363010623e23ef7f716a39ae8b84fff56912860
Timestamp: 1695826552 Timestamp [UCT]: 2023-09-27 14:55:52 Age [y:d:h:m:s]: 01:050:14:54:32
Block: 857344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297420 RingCT/type: yes/0
Extra: 01a7d32995488cf01ba81e7b948363010623e23ef7f716a39ae8b84fff5691286002110000000133af99f4000000000000000000

1 output(s) for total of 0.885652746000 dcy

stealth address amount amount idx
00: 328c8516714b08ab1e97e2b595e02c9dcd7f613a0e4d1b847c97ec00a754903e 0.885652746000 1311460 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": 857354, "vin": [ { "gen": { "height": 857344 } } ], "vout": [ { "amount": 885652746, "target": { "key": "328c8516714b08ab1e97e2b595e02c9dcd7f613a0e4d1b847c97ec00a754903e" } } ], "extra": [ 1, 167, 211, 41, 149, 72, 140, 240, 27, 168, 30, 123, 148, 131, 99, 1, 6, 35, 226, 62, 247, 247, 22, 163, 154, 232, 184, 79, 255, 86, 145, 40, 96, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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