Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a413cae6d49047cb757dd18a39c20add417e5edf0a1c0889abcaee5e3d0a42f7

Tx prefix hash: a26886ddb08796455e284b5b692f16ad5dd0df8cc233177a9f69d9df9c0653e6
Tx public key: 0e0ddb0c867d5f5734322f29e4efe3ae8cae90e50c37c41cc5bcf6412797a2aa
Timestamp: 1726302028 Timestamp [UCT]: 2024-09-14 08:20:28 Age [y:d:h:m:s]: 00:223:14:27:30
Block: 1109795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159640 RingCT/type: yes/0
Extra: 010e0ddb0c867d5f5734322f29e4efe3ae8cae90e50c37c41cc5bcf6412797a2aa021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c34fc2935a622cd8c851c5de2cff58259db4a4c2f7f90520b30abc4b5fca6057 0.600000000000 1588178 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": 1109805, "vin": [ { "gen": { "height": 1109795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c34fc2935a622cd8c851c5de2cff58259db4a4c2f7f90520b30abc4b5fca6057" } } ], "extra": [ 1, 14, 13, 219, 12, 134, 125, 95, 87, 52, 50, 47, 41, 228, 239, 227, 174, 140, 174, 144, 229, 12, 55, 196, 28, 197, 188, 246, 65, 39, 151, 162, 170, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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