Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f39e7a71e1c0383f366bd288f4cc621489810938af873170ab8ca862aa86f8e3

Tx prefix hash: 4f0cc18ca0fcd34c6a1fdc5f36b5effc12f05b6e940cbc544a05df23522d8d2a
Tx public key: e3e96759781a65ed6119d9542e3ad4fb70fb9410f466a1846117139f0a8141ec
Timestamp: 1681615802 Timestamp [UCT]: 2023-04-16 03:30:02 Age [y:d:h:m:s]: 02:206:22:13:54
Block: 739568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 667759 RingCT/type: yes/0
Extra: 01e3e96759781a65ed6119d9542e3ad4fb70fb9410f466a1846117139f0a8141ec0211000000015029cbac000000000000000000

1 output(s) for total of 2.175226198000 dcy

stealth address amount amount idx
00: 6d3ba779436b34e2981c9b98ec6d15247b3cf076e5c15d95570924f6a236f4fe 2.175226198000 1186425 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": 739578, "vin": [ { "gen": { "height": 739568 } } ], "vout": [ { "amount": 2175226198, "target": { "key": "6d3ba779436b34e2981c9b98ec6d15247b3cf076e5c15d95570924f6a236f4fe" } } ], "extra": [ 1, 227, 233, 103, 89, 120, 26, 101, 237, 97, 25, 217, 84, 46, 58, 212, 251, 112, 251, 148, 16, 244, 102, 161, 132, 97, 23, 19, 159, 10, 129, 65, 236, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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