Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a13788c6d3c95fb80f2c5c370dd67e47038a667825e6775071cbb6ccaa45f4f

Tx prefix hash: d4d764bff32fd5133a1681dd3205b2ee08a4169927c0ba8d0fe8e582a22332fe
Tx public key: eceb8fe2b716628c4b2cbecaf8e287600f04959e513fa1363231e5064b6fc275
Timestamp: 1704195493 Timestamp [UCT]: 2024-01-02 11:38:13 Age [y:d:h:m:s]: 01:089:22:57:33
Block: 926517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325395 RingCT/type: yes/0
Extra: 01eceb8fe2b716628c4b2cbecaf8e287600f04959e513fa1363231e5064b6fc27502110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e0bc5c7f5dc3bf442ed4074b29bc42a983cbb73498793979f62355afb1aee4f 0.600000000000 1384303 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": 926527, "vin": [ { "gen": { "height": 926517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e0bc5c7f5dc3bf442ed4074b29bc42a983cbb73498793979f62355afb1aee4f" } } ], "extra": [ 1, 236, 235, 143, 226, 183, 22, 98, 140, 75, 44, 190, 202, 248, 226, 135, 96, 15, 4, 149, 158, 81, 63, 161, 54, 50, 49, 229, 6, 75, 111, 194, 117, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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