Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e01ca8901837d6f41a89ff2212997e98a117a5f15c8f580e520ec890923f7fdf

Tx prefix hash: 28a9b05a86a7b8e016291ad61fc54938af6aed20e7b807fe265562f5d3830d3d
Tx public key: e03f1ffd2e173c7c25a881549dc68bd71028457c835dcab41ce458fb2b7087aa
Timestamp: 1685059125 Timestamp [UCT]: 2023-05-25 23:58:45 Age [y:d:h:m:s]: 01:315:12:06:11
Block: 768126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486709 RingCT/type: yes/0
Extra: 01e03f1ffd2e173c7c25a881549dc68bd71028457c835dcab41ce458fb2b7087aa02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.749362749000 dcy

stealth address amount amount idx
00: 7130515013e523eb75147849041c0ec1abac8485b80d36a5172fcdda86354156 1.749362749000 1217313 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": 768136, "vin": [ { "gen": { "height": 768126 } } ], "vout": [ { "amount": 1749362749, "target": { "key": "7130515013e523eb75147849041c0ec1abac8485b80d36a5172fcdda86354156" } } ], "extra": [ 1, 224, 63, 31, 253, 46, 23, 60, 124, 37, 168, 129, 84, 157, 198, 139, 215, 16, 40, 69, 124, 131, 93, 202, 180, 28, 228, 88, 251, 43, 112, 135, 170, 2, 17, 0, 0, 0, 3, 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