Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a89427560d091d13d923187ecf384dec137658734c9d75a09a56369fc47b0b4f

Tx prefix hash: 03b813d00371f591dcaa092ef1d76376d7266bb1b252ffa3ad70f6e33bfe2b9a
Tx public key: e28b6f9ba9d37e13d7c38cefd0bff80ff3c450a6a314db4b96fd25f6365f8699
Timestamp: 1576643595 Timestamp [UCT]: 2019-12-18 04:33:15 Age [y:d:h:m:s]: 05:051:03:15:54
Block: 28303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184196 RingCT/type: yes/0
Extra: 01e28b6f9ba9d37e13d7c38cefd0bff80ff3c450a6a314db4b96fd25f6365f8699021100000027ad433a0b000000000000000000

1 output(s) for total of 494.562606550000 dcy

stealth address amount amount idx
00: c0d826ac02667a13f6b36b069e1532b5f3d7564a74ef300aedeabc7d10ef99a8 494.562606550000 46847 of 0

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": 28313, "vin": [ { "gen": { "height": 28303 } } ], "vout": [ { "amount": 494562606550, "target": { "key": "c0d826ac02667a13f6b36b069e1532b5f3d7564a74ef300aedeabc7d10ef99a8" } } ], "extra": [ 1, 226, 139, 111, 155, 169, 211, 126, 19, 215, 195, 140, 239, 208, 191, 248, 15, 243, 196, 80, 166, 163, 20, 219, 75, 150, 253, 37, 246, 54, 95, 134, 153, 2, 17, 0, 0, 0, 39, 173, 67, 58, 11, 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