Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 046269901c6ca7c3f7ccaabfb56af11a96048b433a7ede1c31df311ad6ebae7e

Tx prefix hash: a3933a89afd47340b5f743de261dbc3bcfc10534dcb344ff359cfdf8d869d35a
Tx public key: 2f6d6d92ebcd56e2c7da2dc1bf0daf0deb4543d527d7ba5377eb3a1e01aa7e48
Timestamp: 1698569801 Timestamp [UCT]: 2023-10-29 08:56:41 Age [y:d:h:m:s]: 01:117:23:10:54
Block: 880110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345252 RingCT/type: yes/0
Extra: 012f6d6d92ebcd56e2c7da2dc1bf0daf0deb4543d527d7ba5377eb3a1e01aa7e4802110000001e33af99f4000000000000000000

1 output(s) for total of 0.744440910000 dcy

stealth address amount amount idx
00: 59e40b6c65755062fddda1fed33fa50c635cc85af884c62c1d7c21b921b715c7 0.744440910000 1335652 of 0

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": 880120, "vin": [ { "gen": { "height": 880110 } } ], "vout": [ { "amount": 744440910, "target": { "key": "59e40b6c65755062fddda1fed33fa50c635cc85af884c62c1d7c21b921b715c7" } } ], "extra": [ 1, 47, 109, 109, 146, 235, 205, 86, 226, 199, 218, 45, 193, 191, 13, 175, 13, 235, 69, 67, 213, 39, 215, 186, 83, 119, 235, 58, 30, 1, 170, 126, 72, 2, 17, 0, 0, 0, 30, 51, 175, 153, 244, 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