Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 146fd48deddfae39a72578e35f1c7fe55d5c82bfe55e2428dc380738932a1b55

Tx prefix hash: b27816a1f581a88e263783d9054e42c1ab1bb68a0f3d596a66294d6292326068
Tx public key: 231baf3a80eccaa618655a5fcb46c96958b4c023cb19c19dfdf8fe35db6d3165
Timestamp: 1733179741 Timestamp [UCT]: 2024-12-02 22:49:01 Age [y:d:h:m:s]: 00:025:13:01:27
Block: 1166724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18265 RingCT/type: yes/0
Extra: 01231baf3a80eccaa618655a5fcb46c96958b4c023cb19c19dfdf8fe35db6d3165021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f77ff21845187f4bafecf327d701eb747e90a79854f604b2fc47fe8cd2e3d311 0.600000000000 1652413 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": 1166734, "vin": [ { "gen": { "height": 1166724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f77ff21845187f4bafecf327d701eb747e90a79854f604b2fc47fe8cd2e3d311" } } ], "extra": [ 1, 35, 27, 175, 58, 128, 236, 202, 166, 24, 101, 90, 95, 203, 70, 201, 105, 88, 180, 192, 35, 203, 25, 193, 157, 253, 248, 254, 53, 219, 109, 49, 101, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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