Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd540df76e9b46181e2b0f63b4f651703cad073d074d7c36880089ee099fcd36

Tx prefix hash: f179024a19daca0e88209db685fd15ba4efc2b7a4b82d5221faa1d013ed6c742
Tx public key: aec1cb18b6bb343fe6cb33e8545d65c517477078b88c171563bd1686f54ebb17
Timestamp: 1720851816 Timestamp [UCT]: 2024-07-13 06:23:36 Age [y:d:h:m:s]: 00:254:02:09:54
Block: 1064631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181506 RingCT/type: yes/0
Extra: 01aec1cb18b6bb343fe6cb33e8545d65c517477078b88c171563bd1686f54ebb1702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 597025e52d8967e37ecf1acd82a57b9898cb6a12d6b39c2c00e5b66220b3301a 0.600000000000 1535162 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": 1064641, "vin": [ { "gen": { "height": 1064631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "597025e52d8967e37ecf1acd82a57b9898cb6a12d6b39c2c00e5b66220b3301a" } } ], "extra": [ 1, 174, 193, 203, 24, 182, 187, 52, 63, 230, 203, 51, 232, 84, 93, 101, 197, 23, 71, 112, 120, 184, 140, 23, 21, 99, 189, 22, 134, 245, 78, 187, 23, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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