Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a5614bc8f13334d32cda660a7942e2d991a86df3601562ab2926f1d5ae7baf8

Tx prefix hash: 7d79c71c15ed0c80581ea7a5ddc6dc90eb3f9c973f12c595196447bacda6b3d0
Tx public key: 11e80149d21823bdc7504e3fdfc4cdae38439aa640eb4df68b6a51e94097b49d
Timestamp: 1701107725 Timestamp [UCT]: 2023-11-27 17:55:25 Age [y:d:h:m:s]: 01:130:01:21:14
Block: 900928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354108 RingCT/type: yes/0
Extra: 0111e80149d21823bdc7504e3fdfc4cdae38439aa640eb4df68b6a51e94097b49d02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.635113764000 dcy

stealth address amount amount idx
00: a84cbe7d89cdd6c1eba21f767b362bad536250f98157c3cdb27963a0df3f92aa 0.635113764000 1357455 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": 900938, "vin": [ { "gen": { "height": 900928 } } ], "vout": [ { "amount": 635113764, "target": { "key": "a84cbe7d89cdd6c1eba21f767b362bad536250f98157c3cdb27963a0df3f92aa" } } ], "extra": [ 1, 17, 232, 1, 73, 210, 24, 35, 189, 199, 80, 78, 63, 223, 196, 205, 174, 56, 67, 154, 166, 64, 235, 77, 246, 139, 106, 81, 233, 64, 151, 180, 157, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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