Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e7be638ad3e1d7a56a8c846f12c8fd1429424711bd863fe28cff0f75b46ea1c

Tx prefix hash: ae5f6c966717fdfcd33da7d87a5a7e12b01a3ae8e198bc864e3bc45f15c69e51
Tx public key: 3265b799b498079257d57cb4f8891f8044669d4075cfac2377c850b2f31a0829
Timestamp: 1732813249 Timestamp [UCT]: 2024-11-28 17:00:49 Age [y:d:h:m:s]: 00:116:12:44:52
Block: 1163686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83080 RingCT/type: yes/0
Extra: 013265b799b498079257d57cb4f8891f8044669d4075cfac2377c850b2f31a08290211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f54589bf5fc6a0fc3466ff277e8d921159b09dd15dc58672f5603c3a7e0c8f18 0.600000000000 1649353 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": 1163696, "vin": [ { "gen": { "height": 1163686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f54589bf5fc6a0fc3466ff277e8d921159b09dd15dc58672f5603c3a7e0c8f18" } } ], "extra": [ 1, 50, 101, 183, 153, 180, 152, 7, 146, 87, 213, 124, 180, 248, 137, 31, 128, 68, 102, 157, 64, 117, 207, 172, 35, 119, 200, 80, 178, 243, 26, 8, 41, 2, 17, 0, 0, 0, 6, 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