Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 079fcfbb8a0a265a91f6fa768ae1806902e24e79a0b66fccdc32dee813fdd081

Tx prefix hash: 2d113b2ec0b274962bdd0840e4b1e3b20a6170be143b664189d2fd393dae8d4d
Tx public key: 8868ee791ab0df43f766482a7d5cf62d5f58c19bb5a64dfa879b7a9ff81cfc01
Timestamp: 1730941764 Timestamp [UCT]: 2024-11-07 01:09:24 Age [y:d:h:m:s]: 00:000:10:04:18
Block: 1148180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302 RingCT/type: yes/0
Extra: 018868ee791ab0df43f766482a7d5cf62d5f58c19bb5a64dfa879b7a9ff81cfc010211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b604790dad785f2cd574eb96c915c0fd980afcb7d652be6a77a6b6053fa1a9fb 0.600000000000 1632967 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": 1148190, "vin": [ { "gen": { "height": 1148180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b604790dad785f2cd574eb96c915c0fd980afcb7d652be6a77a6b6053fa1a9fb" } } ], "extra": [ 1, 136, 104, 238, 121, 26, 176, 223, 67, 247, 102, 72, 42, 125, 92, 246, 45, 95, 88, 193, 155, 181, 166, 77, 250, 135, 155, 122, 159, 248, 28, 252, 1, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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