Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93b20e86285380a85f730f7d4d6276b462964c4a30e0f73299b28f078bf8afcc

Tx prefix hash: 9521a72ed57cf36ad541ad2a7882c7e13fa0119796dc7eff0ac7bf8d583c46f6
Tx public key: 0b247785d75dcf1d58d444667fe53bc1cbaaa0f7e3de9d966f12fbc332ff8960
Timestamp: 1701064933 Timestamp [UCT]: 2023-11-27 06:02:13 Age [y:d:h:m:s]: 01:053:17:59:06
Block: 900565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299773 RingCT/type: yes/0
Extra: 010b247785d75dcf1d58d444667fe53bc1cbaaa0f7e3de9d966f12fbc332ff89600211000000014b8f5122000000000000000000

1 output(s) for total of 0.636875138000 dcy

stealth address amount amount idx
00: 17ab4f05b6d42ec3cd2b78906fb8e49435e4116a3418a1e00229e26e74f0e66a 0.636875138000 1357072 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": 900575, "vin": [ { "gen": { "height": 900565 } } ], "vout": [ { "amount": 636875138, "target": { "key": "17ab4f05b6d42ec3cd2b78906fb8e49435e4116a3418a1e00229e26e74f0e66a" } } ], "extra": [ 1, 11, 36, 119, 133, 215, 93, 207, 29, 88, 212, 68, 102, 127, 229, 59, 193, 203, 170, 160, 247, 227, 222, 157, 150, 111, 18, 251, 195, 50, 255, 137, 96, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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