Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e8bd3be557230a097d4604ef46e8be336920b6be6443193d460be8cc09e6c17

Tx prefix hash: b900d278dac3aa4e374ba52947ea991c69b739501c2ca2a84f2efb74da62b66c
Tx public key: c78e0e57eb54a72c97a951b023ef68cfa66c257e49990036a87f6664b94d00ee
Timestamp: 1711509160 Timestamp [UCT]: 2024-03-27 03:12:40 Age [y:d:h:m:s]: 01:232:10:06:19
Block: 987185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424785 RingCT/type: yes/0
Extra: 01c78e0e57eb54a72c97a951b023ef68cfa66c257e49990036a87f6664b94d00ee02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7737d08860e6bab1889f2415948a69d16950d5b0ff472d4494b7fe1d64659b7 0.600000000000 1447426 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": 987195, "vin": [ { "gen": { "height": 987185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7737d08860e6bab1889f2415948a69d16950d5b0ff472d4494b7fe1d64659b7" } } ], "extra": [ 1, 199, 142, 14, 87, 235, 84, 167, 44, 151, 169, 81, 176, 35, 239, 104, 207, 166, 108, 37, 126, 73, 153, 0, 54, 168, 127, 102, 100, 185, 77, 0, 238, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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