Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79e123b51b15bd43060756a62ce6389503b030756eb81b91cfe40d65abb0a86e

Tx prefix hash: 345c5cba8cc784091c964492d0d5d6211cfb8b612466768636a372ecd022e63e
Tx public key: 9a9a15b159b1ed5a0279e1ad5915dff36bce172ef87f628335e2fd413ea4dfad
Timestamp: 1728233812 Timestamp [UCT]: 2024-10-06 16:56:52 Age [y:d:h:m:s]: 00:219:12:14:47
Block: 1125820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156707 RingCT/type: yes/0
Extra: 019a9a15b159b1ed5a0279e1ad5915dff36bce172ef87f628335e2fd413ea4dfad02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bd5bdd7cfac2f760e8796c023074a863f6a5803a3c432c6d0d6f74cc7af79b0 0.600000000000 1608573 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": 1125830, "vin": [ { "gen": { "height": 1125820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bd5bdd7cfac2f760e8796c023074a863f6a5803a3c432c6d0d6f74cc7af79b0" } } ], "extra": [ 1, 154, 154, 21, 177, 89, 177, 237, 90, 2, 121, 225, 173, 89, 21, 223, 243, 107, 206, 23, 46, 248, 127, 98, 131, 53, 226, 253, 65, 62, 164, 223, 173, 2, 17, 0, 0, 0, 5, 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