Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbb3d4d43cd1316c83dfc38c6fe1a8cb476c7478e93bd0780c8dd67e3dafc716

Tx prefix hash: f84f217c9e44f92e67c9983487fb52358994cb08a8f3e4579499368471921626
Tx public key: c1d9e0e73ca9f7f84469d5a93547dd2591a1aef0d13aa7193be53fa02a77d757
Timestamp: 1745560137 Timestamp [UCT]: 2025-04-25 05:48:57 Age [y:d:h:m:s]: 00:245:12:09:16
Block: 1268950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173227 RingCT/type: yes/0
Extra: 01c1d9e0e73ca9f7f84469d5a93547dd2591a1aef0d13aa7193be53fa02a77d757021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 567f983ed8aa993cbf72cff13a28d29b50c973b64379e6873ae298df4bd1c84f 0.600000000000 1756183 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": 1268960, "vin": [ { "gen": { "height": 1268950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "567f983ed8aa993cbf72cff13a28d29b50c973b64379e6873ae298df4bd1c84f" } } ], "extra": [ 1, 193, 217, 224, 231, 60, 169, 247, 248, 68, 105, 213, 169, 53, 71, 221, 37, 145, 161, 174, 240, 209, 58, 167, 25, 59, 229, 63, 160, 42, 119, 215, 87, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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