Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cfe46701917cd1cf68e9882cfba610d9fb450632a701633517be2bd0bfae86b

Tx prefix hash: f0271d652150a036e918b99d834eaa44e879e513250dbc6439ff3f44111f0b4e
Tx public key: ef5b84d9e670ad329c0ccd7ea1b9baf4f3a3dde289eba5f2ab08e7bb37a21a84
Timestamp: 1725358458 Timestamp [UCT]: 2024-09-03 10:14:18 Age [y:d:h:m:s]: 00:050:01:02:07
Block: 1101989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35809 RingCT/type: yes/0
Extra: 01ef5b84d9e670ad329c0ccd7ea1b9baf4f3a3dde289eba5f2ab08e7bb37a21a8402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cddbb6526d79b164b4e22e5c1660e40caf5298119ec372cdeb30cc56603c4553 0.600000000000 1578248 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": 1101999, "vin": [ { "gen": { "height": 1101989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cddbb6526d79b164b4e22e5c1660e40caf5298119ec372cdeb30cc56603c4553" } } ], "extra": [ 1, 239, 91, 132, 217, 230, 112, 173, 50, 156, 12, 205, 126, 161, 185, 186, 244, 243, 163, 221, 226, 137, 235, 165, 242, 171, 8, 231, 187, 55, 162, 26, 132, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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