Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864a3fcb91b695eda3e9299cb72ea6ba217757b4d2db95f04ea3dcb9aa8c79a4

Tx prefix hash: efe50085fb6b903aa743f060941070678d8c0f56693a69aa58356ff5fd27efc1
Tx public key: cbb1c747d6751bfb997e2ca67b0f5fa6c9d0b267ba8466a2adf9702230380aba
Timestamp: 1708795400 Timestamp [UCT]: 2024-02-24 17:23:20 Age [y:d:h:m:s]: 01:021:19:26:10
Block: 964677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276606 RingCT/type: yes/0
Extra: 01cbb1c747d6751bfb997e2ca67b0f5fa6c9d0b267ba8466a2adf9702230380aba021100000006679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8c57ee41cb624511adfb0565a50995c76675af03db2f690ccac8a15b55442f6 0.600000000000 1424418 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": 964687, "vin": [ { "gen": { "height": 964677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8c57ee41cb624511adfb0565a50995c76675af03db2f690ccac8a15b55442f6" } } ], "extra": [ 1, 203, 177, 199, 71, 214, 117, 27, 251, 153, 126, 44, 166, 123, 15, 95, 166, 201, 208, 178, 103, 186, 132, 102, 162, 173, 249, 112, 34, 48, 56, 10, 186, 2, 17, 0, 0, 0, 6, 103, 154, 138, 129, 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