Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1e3adb59a70fba47ad9a5a86c0c56daa35509d085702555a391fa2cf107d329

Tx prefix hash: 14ce2240f866a0488826a08bccb325a12bc651f71bf94b7813cbdb0cb2df8d51
Tx public key: c4ba4c86e5dcf5ed78d1afb40fc2252109e5d1dd23c6a04959f5db0dd55d3917
Timestamp: 1733545422 Timestamp [UCT]: 2024-12-07 04:23:42 Age [y:d:h:m:s]: 00:110:20:48:48
Block: 1169746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79030 RingCT/type: yes/0
Extra: 01c4ba4c86e5dcf5ed78d1afb40fc2252109e5d1dd23c6a04959f5db0dd55d39170211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17d5929b9cc943f97757340853abf359e2d7140b60d8fb8ec0e87ffe25f43615 0.600000000000 1655469 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": 1169756, "vin": [ { "gen": { "height": 1169746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17d5929b9cc943f97757340853abf359e2d7140b60d8fb8ec0e87ffe25f43615" } } ], "extra": [ 1, 196, 186, 76, 134, 229, 220, 245, 237, 120, 209, 175, 180, 15, 194, 37, 33, 9, 229, 209, 221, 35, 198, 160, 73, 89, 245, 219, 13, 213, 93, 57, 23, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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