Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24dfe01bb867609a4df57ffe015a0b411c1b96ddfaa8ca3be36181e16df3d081

Tx prefix hash: 74a2d764db090bc7259377836fc29130b724c079aef4bf7189c8f4bc4a3bcb0c
Tx public key: 3e1e526679a9659422a0de7d4d9aaf401120744317b334b41e63c8c2c740d2a3
Timestamp: 1685080807 Timestamp [UCT]: 2023-05-26 06:00:07 Age [y:d:h:m:s]: 01:212:01:05:15
Block: 768305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413001 RingCT/type: yes/0
Extra: 013e1e526679a9659422a0de7d4d9aaf401120744317b334b41e63c8c2c740d2a302110000000233af99f4000000000000000000

1 output(s) for total of 1.746975333000 dcy

stealth address amount amount idx
00: 01db695e5c41d6f326247b93d73f2d2b41cb97ea4ffae1f100ec1e161ca74795 1.746975333000 1217498 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": 768315, "vin": [ { "gen": { "height": 768305 } } ], "vout": [ { "amount": 1746975333, "target": { "key": "01db695e5c41d6f326247b93d73f2d2b41cb97ea4ffae1f100ec1e161ca74795" } } ], "extra": [ 1, 62, 30, 82, 102, 121, 169, 101, 148, 34, 160, 222, 125, 77, 154, 175, 64, 17, 32, 116, 67, 23, 179, 52, 180, 30, 99, 200, 194, 199, 64, 210, 163, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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