Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5848f35670c7f1e3e39c9304b788af588c42dd931a3bdf79d4a537ea3e3f954

Tx prefix hash: 3ba88acea5a515ecfff3c9605ba0596bafe761c7d961c118b4a0f0b8ddbde2ac
Tx public key: e15643eebf7526b449920ab63411d004eb515a277376d2d89a60daa4b98baa8a
Timestamp: 1696720624 Timestamp [UCT]: 2023-10-07 23:17:04 Age [y:d:h:m:s]: 01:254:07:34:46
Block: 864765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442722 RingCT/type: yes/0
Extra: 01e15643eebf7526b449920ab63411d004eb515a277376d2d89a60daa4b98baa8a0211000000014b8f5122000000000000000000

1 output(s) for total of 0.836902006000 dcy

stealth address amount amount idx
00: 2fe8b0944c9b16300064ba47958d1c92aa7d864f2318a3d345818b210abb2288 0.836902006000 1319285 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": 864775, "vin": [ { "gen": { "height": 864765 } } ], "vout": [ { "amount": 836902006, "target": { "key": "2fe8b0944c9b16300064ba47958d1c92aa7d864f2318a3d345818b210abb2288" } } ], "extra": [ 1, 225, 86, 67, 238, 191, 117, 38, 180, 73, 146, 10, 182, 52, 17, 208, 4, 235, 81, 90, 39, 115, 118, 210, 216, 154, 96, 218, 164, 185, 139, 170, 138, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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