Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2e99f27a8fceb6169a65fe3c3e085cb31a486878a5e9dff20c5973262a49070

Tx prefix hash: 6d7bfa084695e79a8a7c25873911ac41c8b6fa2c7b804e38488090463e2f320c
Tx public key: ee54164ae110e560a1ff3e5054eceed6cb83ce9b1e6c2f0c3fcc3196684918ff
Timestamp: 1694724808 Timestamp [UCT]: 2023-09-14 20:53:28 Age [y:d:h:m:s]: 01:204:09:58:19
Block: 848195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407188 RingCT/type: yes/0
Extra: 01ee54164ae110e560a1ff3e5054eceed6cb83ce9b1e6c2f0c3fcc3196684918ff0211000000094b8f5122000000000000000000

1 output(s) for total of 0.949681377000 dcy

stealth address amount amount idx
00: 2310d4103e722fe43528f5bd749ae2521a3b33bbabbbfa333602e10f74c60c6e 0.949681377000 1301783 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": 848205, "vin": [ { "gen": { "height": 848195 } } ], "vout": [ { "amount": 949681377, "target": { "key": "2310d4103e722fe43528f5bd749ae2521a3b33bbabbbfa333602e10f74c60c6e" } } ], "extra": [ 1, 238, 84, 22, 74, 225, 16, 229, 96, 161, 255, 62, 80, 84, 236, 238, 214, 203, 131, 206, 155, 30, 108, 47, 12, 63, 204, 49, 150, 104, 73, 24, 255, 2, 17, 0, 0, 0, 9, 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