Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07b730a8c736ff78c6c9f75fa60cc0c4f4e6b38fbe7173fc73811fc2a6fe88d8

Tx prefix hash: af5c99cfaf6d8961d909d8d686f1793eeec7ed1f22b9ebd46b2888dc3d7b1e07
Tx public key: c8818d7c520741e8fc5304a3417fbc2cdffd6f05b670eb52a7f97567e0cb7cce
Timestamp: 1718364419 Timestamp [UCT]: 2024-06-14 11:26:59 Age [y:d:h:m:s]: 00:222:12:34:44
Block: 1044000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159197 RingCT/type: yes/0
Extra: 01c8818d7c520741e8fc5304a3417fbc2cdffd6f05b670eb52a7f97567e0cb7cce0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc4c5f76292fd518d1dce05f42e4fce076b741abb813c9e37ba6e7ab0514d286 0.600000000000 1513189 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": 1044010, "vin": [ { "gen": { "height": 1044000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc4c5f76292fd518d1dce05f42e4fce076b741abb813c9e37ba6e7ab0514d286" } } ], "extra": [ 1, 200, 129, 141, 124, 82, 7, 65, 232, 252, 83, 4, 163, 65, 127, 188, 44, 223, 253, 111, 5, 182, 112, 235, 82, 167, 249, 117, 103, 224, 203, 124, 206, 2, 17, 0, 0, 0, 1, 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