Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 432d3137e8488b2766caf540e5d70ef3bde045f55bce8791d842a7f12a5b9214

Tx prefix hash: 13a29d26aa811d07c6df9ebee64bfc411d704e4157f001fdf08209d90a25ac74
Tx public key: 3b759395096164bb28ee53b671ef0dbaecbdaae57c0cefcefd86869d623f58da
Timestamp: 1709313944 Timestamp [UCT]: 2024-03-01 17:25:44 Age [y:d:h:m:s]: 01:041:23:30:17
Block: 968971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291007 RingCT/type: yes/0
Extra: 013b759395096164bb28ee53b671ef0dbaecbdaae57c0cefcefd86869d623f58da0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21f130c6f647e86e852d7cdb89840306433391f972d681efcfd4a2c3f8c7c57a 0.600000000000 1428798 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": 968981, "vin": [ { "gen": { "height": 968971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21f130c6f647e86e852d7cdb89840306433391f972d681efcfd4a2c3f8c7c57a" } } ], "extra": [ 1, 59, 117, 147, 149, 9, 97, 100, 187, 40, 238, 83, 182, 113, 239, 13, 186, 236, 189, 170, 229, 124, 12, 239, 206, 253, 134, 134, 157, 98, 63, 88, 218, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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