Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 235c7ce37735a01017f3f24c041fa8655456bbee0ee3e0f363dcce8300c00a21

Tx prefix hash: bd725e4c65bba4d621693f7c4b8e596e535d56d13715ad1f838d26bca3f65e7f
Tx public key: c85238ed8fc8d53bce8d74cf199fcb373c077e4c02084eb5dd7d71098c138244
Timestamp: 1730563525 Timestamp [UCT]: 2024-11-02 16:05:25 Age [y:d:h:m:s]: 00:208:08:36:26
Block: 1145046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148795 RingCT/type: yes/0
Extra: 01c85238ed8fc8d53bce8d74cf199fcb373c077e4c02084eb5dd7d71098c13824402110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc16fa894b3791978885e65a9f263b375e538800a9442924dc2b4e4d38a5bc8e 0.600000000000 1629411 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": 1145056, "vin": [ { "gen": { "height": 1145046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc16fa894b3791978885e65a9f263b375e538800a9442924dc2b4e4d38a5bc8e" } } ], "extra": [ 1, 200, 82, 56, 237, 143, 200, 213, 59, 206, 141, 116, 207, 25, 159, 203, 55, 60, 7, 126, 76, 2, 8, 78, 181, 221, 125, 113, 9, 140, 19, 130, 68, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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