Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26d2d477232a41d5be1be954a013b7df49bac99f17ea2e681967af04dfb5d659

Tx prefix hash: bcb0fdad7ce740b05a2d8c209a1eeef2c2d24e07e71983cd89b63b70fdeb5bf7
Tx public key: 5f2c3fcc6dcb0efe79443a93d8813bbc91cd1c8fbed4821c4dbe74d5b8fe04e4
Timestamp: 1573984627 Timestamp [UCT]: 2019-11-17 09:57:07 Age [y:d:h:m:s]: 05:011:01:25:22
Block: 10362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1151723 RingCT/type: yes/0
Extra: 015f2c3fcc6dcb0efe79443a93d8813bbc91cd1c8fbed4821c4dbe74d5b8fe04e4

1 output(s) for total of 567.109971399000 dcy

stealth address amount amount idx
00: 4aefa8f93a31bcbc52330252db9f5eebf014da696b459bda4948635f81704e68 567.109971399000 11405 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": 10372, "vin": [ { "gen": { "height": 10362 } } ], "vout": [ { "amount": 567109971399, "target": { "key": "4aefa8f93a31bcbc52330252db9f5eebf014da696b459bda4948635f81704e68" } } ], "extra": [ 1, 95, 44, 63, 204, 109, 203, 14, 254, 121, 68, 58, 147, 216, 129, 59, 188, 145, 205, 28, 143, 190, 212, 130, 28, 77, 190, 116, 213, 184, 254, 4, 228 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8