Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c3751a3d4ea9a02a43e7783daff2f4009719fadc45144eaf101f9503eb3a477

Tx prefix hash: 3eaac8b4e69b21440d10f8591119e6ab5ac46cf3fd6a37e85cc11436889c836e
Tx public key: 3636ef57f8ea89a7293e9a411e15e7f26b9a84f391fbafe5230e38b369203810
Timestamp: 1716524329 Timestamp [UCT]: 2024-05-24 04:18:49 Age [y:d:h:m:s]: 00:299:06:06:59
Block: 1028755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213885 RingCT/type: yes/0
Extra: 013636ef57f8ea89a7293e9a411e15e7f26b9a84f391fbafe5230e38b36920381002110000001252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26d04f3984d40e1f46b54ecbd9c64158e4a96dc439dcad6051e2bd07d4d9fc7f 0.600000000000 1496752 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": 1028765, "vin": [ { "gen": { "height": 1028755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26d04f3984d40e1f46b54ecbd9c64158e4a96dc439dcad6051e2bd07d4d9fc7f" } } ], "extra": [ 1, 54, 54, 239, 87, 248, 234, 137, 167, 41, 62, 154, 65, 30, 21, 231, 242, 107, 154, 132, 243, 145, 251, 175, 229, 35, 14, 56, 179, 105, 32, 56, 16, 2, 17, 0, 0, 0, 18, 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