Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd4f666cfd3de516cf31476f8ea22b47da0871419199d16d202eb0429ebc29b0

Tx prefix hash: 9179e1f68c024326de9d64cb7ae4342625ef8b8ccd16ab0ff44f519a9ac8dab7
Tx public key: 295cbb554086d9e11bc692cd19c126a077c288dff700e8a59c7d84a96bbc2d79
Timestamp: 1716199606 Timestamp [UCT]: 2024-05-20 10:06:46 Age [y:d:h:m:s]: 00:282:05:09:38
Block: 1026053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201683 RingCT/type: yes/0
Extra: 01295cbb554086d9e11bc692cd19c126a077c288dff700e8a59c7d84a96bbc2d7902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53051c0f958e1c3bbf06f4b040279d94a427755a5109b9d00833c0f9910380d3 0.600000000000 1492924 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": 1026063, "vin": [ { "gen": { "height": 1026053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53051c0f958e1c3bbf06f4b040279d94a427755a5109b9d00833c0f9910380d3" } } ], "extra": [ 1, 41, 92, 187, 85, 64, 134, 217, 225, 27, 198, 146, 205, 25, 193, 38, 160, 119, 194, 136, 223, 247, 0, 232, 165, 156, 125, 132, 169, 107, 188, 45, 121, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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