Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2343910bd89c87c83f33258b0c5af8409ef86988a5f3b3a8d79afb25e2ce7e0

Tx prefix hash: 6d38db4ef8b1a10616d4d26d61d18e05cc5179cc83f85ce1f7fc39f133346bb8
Tx public key: 8f832792154ca0b4cf8e137d5b1ef714c35cf2d0c7ee42ce59a232c7727bf77f
Timestamp: 1578088598 Timestamp [UCT]: 2020-01-03 21:56:38 Age [y:d:h:m:s]: 05:030:13:47:07
Block: 38027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171731 RingCT/type: yes/0
Extra: 018f832792154ca0b4cf8e137d5b1ef714c35cf2d0c7ee42ce59a232c7727bf77f0211000000dd597126dd000000000000000000

1 output(s) for total of 459.199719143000 dcy

stealth address amount amount idx
00: c50fc3e9725e0daac3865954b066527053952be0b64384dc1e55108d3a5569a6 459.199719143000 64664 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": 38037, "vin": [ { "gen": { "height": 38027 } } ], "vout": [ { "amount": 459199719143, "target": { "key": "c50fc3e9725e0daac3865954b066527053952be0b64384dc1e55108d3a5569a6" } } ], "extra": [ 1, 143, 131, 39, 146, 21, 76, 160, 180, 207, 142, 19, 125, 91, 30, 247, 20, 195, 92, 242, 208, 199, 238, 66, 206, 89, 162, 50, 199, 114, 123, 247, 127, 2, 17, 0, 0, 0, 221, 89, 113, 38, 221, 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