Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5719c6f9fbf1ffabfa699625025238ef5e4a7661c35b8255d403115372ad0122

Tx prefix hash: 051d84ece15856a7195377b25f5d77764bba4d25d9ea0a5b9b65ed45f0d70374
Tx public key: 3375b2a24a989a9faee332b13692074caeabdc891ae8a5f33e13b97c8866aeb5
Timestamp: 1728478536 Timestamp [UCT]: 2024-10-09 12:55:36 Age [y:d:h:m:s]: 00:176:13:08:58
Block: 1127844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125961 RingCT/type: yes/0
Extra: 013375b2a24a989a9faee332b13692074caeabdc891ae8a5f33e13b97c8866aeb502110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4a736a31cbd220ef35d2c13651b76f5132afe7f4be0f63b65ff8601b4d383f4 0.600000000000 1610657 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": 1127854, "vin": [ { "gen": { "height": 1127844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4a736a31cbd220ef35d2c13651b76f5132afe7f4be0f63b65ff8601b4d383f4" } } ], "extra": [ 1, 51, 117, 178, 162, 74, 152, 154, 159, 174, 227, 50, 177, 54, 146, 7, 76, 174, 171, 220, 137, 26, 232, 165, 243, 62, 19, 185, 124, 136, 102, 174, 181, 2, 17, 0, 0, 0, 10, 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