Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9dc79a0a54c1d9504d5ac40caa468a3c804ebff3211f212513390423020da33

Tx prefix hash: e8971c48138799dd4a40a9b41cb91188eca1167c0ee5230618cd5c5e7efa2357
Tx public key: 31ae49a31827475a84dd8a2550da90254c02b6f06702105c1bafe6666d07c963
Timestamp: 1709402287 Timestamp [UCT]: 2024-03-02 17:58:07 Age [y:d:h:m:s]: 01:035:10:47:10
Block: 969708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286317 RingCT/type: yes/0
Extra: 0131ae49a31827475a84dd8a2550da90254c02b6f06702105c1bafe6666d07c963021100000001cdf2b46b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2d4663e0d528ef8bfdc09881faeda8e8214ae5adccf3f1a7beb9fb620955b83 0.600000000000 1429545 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": 969718, "vin": [ { "gen": { "height": 969708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2d4663e0d528ef8bfdc09881faeda8e8214ae5adccf3f1a7beb9fb620955b83" } } ], "extra": [ 1, 49, 174, 73, 163, 24, 39, 71, 90, 132, 221, 138, 37, 80, 218, 144, 37, 76, 2, 182, 240, 103, 2, 16, 92, 27, 175, 230, 102, 109, 7, 201, 99, 2, 17, 0, 0, 0, 1, 205, 242, 180, 107, 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