Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa48a0cbaddf32a34befd76121c4e45d402fc6a066a72165c058796e18e7b5da

Tx prefix hash: 1ef3408087f081692c50c58c5afc50585e21b136240ce2300d53634da7e7d24d
Tx public key: 7a005b702bd84da8c504361fc56d8b7d61872b4b6d859c435b275bcfefb5a219
Timestamp: 1720189424 Timestamp [UCT]: 2024-07-05 14:23:44 Age [y:d:h:m:s]: 00:225:22:13:01
Block: 1059122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161363 RingCT/type: yes/0
Extra: 017a005b702bd84da8c504361fc56d8b7d61872b4b6d859c435b275bcfefb5a2190211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c49dcbbcc5bb8a6c578de80107ca1fb99325141f8e229b33bcbf028966911b70 0.600000000000 1529583 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": 1059132, "vin": [ { "gen": { "height": 1059122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c49dcbbcc5bb8a6c578de80107ca1fb99325141f8e229b33bcbf028966911b70" } } ], "extra": [ 1, 122, 0, 91, 112, 43, 216, 77, 168, 197, 4, 54, 31, 197, 109, 139, 125, 97, 135, 43, 75, 109, 133, 156, 67, 91, 39, 91, 207, 239, 181, 162, 25, 2, 17, 0, 0, 0, 7, 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