Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 602dbc2ca7b695618a2a4bbca4bc734a71e14e7cd95a50c287bd9760ee2b2a5b

Tx prefix hash: 606371e56a8c3de2323c8835839fbd9204ea8089a44dce77055fea8b21efbdd0
Tx public key: d9a6fa3cf48f9d3605e968617011928a8ab4f30b23157ecc87f3a2ebbdd1d07b
Timestamp: 1723964786 Timestamp [UCT]: 2024-08-18 07:06:26 Age [y:d:h:m:s]: 00:221:20:25:11
Block: 1090434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158407 RingCT/type: yes/0
Extra: 01d9a6fa3cf48f9d3605e968617011928a8ab4f30b23157ecc87f3a2ebbdd1d07b02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3384b9dae6f438c1920a2142472ecf6a6a42f58c536f41d8703aca1461b3ff9 0.600000000000 1565057 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": 1090444, "vin": [ { "gen": { "height": 1090434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3384b9dae6f438c1920a2142472ecf6a6a42f58c536f41d8703aca1461b3ff9" } } ], "extra": [ 1, 217, 166, 250, 60, 244, 143, 157, 54, 5, 233, 104, 97, 112, 17, 146, 138, 138, 180, 243, 11, 35, 21, 126, 204, 135, 243, 162, 235, 189, 209, 208, 123, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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