Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1acd49564016adef32533b0d463860f8b8f8ad7d05b9af93174371534c5ba0

Tx prefix hash: d0a72ca0c7ca88bc34b042f83309586a8ea0b7d2a5c9725029e39f61cb5e7c41
Tx public key: a916bd6783cab7f781f0368f3417292af3014fbd97be3f6968ad08c497775bb1
Timestamp: 1696725301 Timestamp [UCT]: 2023-10-08 00:35:01 Age [y:d:h:m:s]: 01:183:17:54:58
Block: 864802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392356 RingCT/type: yes/0
Extra: 01a916bd6783cab7f781f0368f3417292af3014fbd97be3f6968ad08c497775bb102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.836665792000 dcy

stealth address amount amount idx
00: 82265a9cb70ad8ab36f6818fa435acb6c4eecc048fd36a3dd920692ec271dcf6 0.836665792000 1319322 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": 864812, "vin": [ { "gen": { "height": 864802 } } ], "vout": [ { "amount": 836665792, "target": { "key": "82265a9cb70ad8ab36f6818fa435acb6c4eecc048fd36a3dd920692ec271dcf6" } } ], "extra": [ 1, 169, 22, 189, 103, 131, 202, 183, 247, 129, 240, 54, 143, 52, 23, 41, 42, 243, 1, 79, 189, 151, 190, 63, 105, 104, 173, 8, 196, 151, 119, 91, 177, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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