Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d52ff7182d3bbf5b8456f685dae8bdeca66609adb0c50cbf7d4d9cf477b9fd10

Tx prefix hash: b6ad9d6522a90a896530b25fdc71f11cfa382946c26756f19be192906c8a20d9
Tx public key: b997238db2402af3ad240ad4e8546524048e7a9d2047378f25e2eb1fb02f5f9b
Timestamp: 1727966843 Timestamp [UCT]: 2024-10-03 14:47:23 Age [y:d:h:m:s]: 01:090:03:12:02
Block: 1123612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322867 RingCT/type: yes/0
Extra: 01b997238db2402af3ad240ad4e8546524048e7a9d2047378f25e2eb1fb02f5f9b02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8f1add6ce342a545efad77583eb76b1d5e12640ae87e91091a76c13d0bc4347 0.600000000000 1606147 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": 1123622, "vin": [ { "gen": { "height": 1123612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8f1add6ce342a545efad77583eb76b1d5e12640ae87e91091a76c13d0bc4347" } } ], "extra": [ 1, 185, 151, 35, 141, 178, 64, 42, 243, 173, 36, 10, 212, 232, 84, 101, 36, 4, 142, 122, 157, 32, 71, 55, 143, 37, 226, 235, 31, 176, 47, 95, 155, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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