Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b3be65b132faefdfb9849812b439510f4ac1b68c6614038d47f1ebe02d5a86e

Tx prefix hash: 25affb0c4e9d8a89cc94d014eb74f8b0633af3d695ed7ed2a50780d2115ff00a
Tx public key: 4332c84eaec3e75627f4a0eacd974a1da73410a46fb38dc049b60c36ed804e70
Timestamp: 1735229395 Timestamp [UCT]: 2024-12-26 16:09:55 Age [y:d:h:m:s]: 00:173:09:49:59
Block: 1183686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123652 RingCT/type: yes/0
Extra: 014332c84eaec3e75627f4a0eacd974a1da73410a46fb38dc049b60c36ed804e700211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 452a7345024e4d0dbddb2ef233154911846d79084d96d803d2bb83ac16cd6d1f 0.600000000000 1670133 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": 1183696, "vin": [ { "gen": { "height": 1183686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "452a7345024e4d0dbddb2ef233154911846d79084d96d803d2bb83ac16cd6d1f" } } ], "extra": [ 1, 67, 50, 200, 78, 174, 195, 231, 86, 39, 244, 160, 234, 205, 151, 74, 29, 167, 52, 16, 164, 111, 179, 141, 192, 73, 182, 12, 54, 237, 128, 78, 112, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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