Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6adb542e178302729aaba4f20f7e821cebfc3cfe6d2598cf1eb50dbc6481f95

Tx prefix hash: acbb6a4a907cc7c7704024a302c9c53e1c48282cf392221a59e8cc1d482ec1e2
Tx public key: 840616b642e8c77f09533eef440aae9a20821f9bd5d481299dce7247e4d6e8a6
Timestamp: 1717197962 Timestamp [UCT]: 2024-05-31 23:26:02 Age [y:d:h:m:s]: 00:307:14:38:35
Block: 1034324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219846 RingCT/type: yes/0
Extra: 01840616b642e8c77f09533eef440aae9a20821f9bd5d481299dce7247e4d6e8a602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b702f7251d182c208a5da1a805556b0a82c79a27f21599d1b772d39c1d4f79d3 0.600000000000 1502827 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": 1034334, "vin": [ { "gen": { "height": 1034324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b702f7251d182c208a5da1a805556b0a82c79a27f21599d1b772d39c1d4f79d3" } } ], "extra": [ 1, 132, 6, 22, 182, 66, 232, 199, 127, 9, 83, 62, 239, 68, 10, 174, 154, 32, 130, 31, 155, 213, 212, 129, 41, 157, 206, 114, 71, 228, 214, 232, 166, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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