Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e7a4556555c6f0f9e4a2310379db92fb6f134172bbb649f78edd3547cb5608a

Tx prefix hash: a843fc349434a6a39c5ccce1504cdd7ba000a6014dce846290609284ad194710
Tx public key: 949e63d5b26183d4634f2709e55e2ee69d6abfa6733c46df89e0df3f52dc59df
Timestamp: 1704687887 Timestamp [UCT]: 2024-01-08 04:24:47 Age [y:d:h:m:s]: 01:016:20:57:00
Block: 930590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273364 RingCT/type: yes/0
Extra: 01949e63d5b26183d4634f2709e55e2ee69d6abfa6733c46df89e0df3f52dc59df0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33ea836e92ad6cab2d76c40cbd67c55156417dbe9200fc1c581e66639e254e40 0.600000000000 1388474 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": 930600, "vin": [ { "gen": { "height": 930590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33ea836e92ad6cab2d76c40cbd67c55156417dbe9200fc1c581e66639e254e40" } } ], "extra": [ 1, 148, 158, 99, 213, 178, 97, 131, 212, 99, 79, 39, 9, 229, 94, 46, 230, 157, 106, 191, 166, 115, 60, 70, 223, 137, 224, 223, 63, 82, 220, 89, 223, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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