Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edddd967fcda7aa8ba8e603550031d9111248e618b8161b1498ea84f75602f9b

Tx prefix hash: b0195bf70cbf101850746dd84c38dd4728a98985adf783d9b078181bf91e6b13
Tx public key: 39ea9ce97c052f9e26ff1af3dfbae51b86279a01fa31a9f66fc751bb2860a1d9
Timestamp: 1703699243 Timestamp [UCT]: 2023-12-27 17:47:23 Age [y:d:h:m:s]: 01:031:23:03:08
Block: 922409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283947 RingCT/type: yes/0
Extra: 0139ea9ce97c052f9e26ff1af3dfbae51b86279a01fa31a9f66fc751bb2860a1d902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3f6bb5bac14e80382b6cebc2caa2afae38a00ac2c2ebf6a0cec3e9d775b33fd 0.600000000000 1380105 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": 922419, "vin": [ { "gen": { "height": 922409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3f6bb5bac14e80382b6cebc2caa2afae38a00ac2c2ebf6a0cec3e9d775b33fd" } } ], "extra": [ 1, 57, 234, 156, 233, 124, 5, 47, 158, 38, 255, 26, 243, 223, 186, 229, 27, 134, 39, 154, 1, 250, 49, 169, 246, 111, 199, 81, 187, 40, 96, 161, 217, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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