Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eb0f165fedff5c7411efca68efeed29307fa6cadefc37b8685195c1c43b5620

Tx prefix hash: c4deb7b91e056f65d098f5cee5bfe7b99bb31cd77147de35998f56ac469fc1bf
Tx public key: 10a440fb81338d3a00d3748303809912fd9e679b54f80d3a8fdc2fb83a9d2b95
Timestamp: 1722917652 Timestamp [UCT]: 2024-08-06 04:14:12 Age [y:d:h:m:s]: 00:314:01:34:00
Block: 1081740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224304 RingCT/type: yes/0
Extra: 0110a440fb81338d3a00d3748303809912fd9e679b54f80d3a8fdc2fb83a9d2b95021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa341d284454e6b0ca56510880e608c098a0b584e84a6878561c0af654c620f9 0.600000000000 1555561 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": 1081750, "vin": [ { "gen": { "height": 1081740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa341d284454e6b0ca56510880e608c098a0b584e84a6878561c0af654c620f9" } } ], "extra": [ 1, 16, 164, 64, 251, 129, 51, 141, 58, 0, 211, 116, 131, 3, 128, 153, 18, 253, 158, 103, 155, 84, 248, 13, 58, 143, 220, 47, 184, 58, 157, 43, 149, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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