Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f90abdb5fda8a2d74ee6511572121edba92d5601e6ccad9c9af53802950e87d9

Tx prefix hash: a6168e4db83d151eb9526b387e5b5418ac14ebcaa9902fa13919087aa7f0ba8f
Tx public key: 0ee92125796a7446757c8921a3bb9c715b9fdc34e53b332fdd0c8a95d0e53276
Timestamp: 1673127263 Timestamp [UCT]: 2023-01-07 21:34:23 Age [y:d:h:m:s]: 02:125:13:39:43
Block: 669819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 611447 RingCT/type: yes/0
Extra: 010ee92125796a7446757c8921a3bb9c715b9fdc34e53b332fdd0c8a95d0e5327602110000000374b6d784000000000000000000

1 output(s) for total of 3.703493233000 dcy

stealth address amount amount idx
00: a5c7a283fc5ccbc5f4d501a705c99e5bc762273e1c1f84ab4d70a9a8e0dc54e8 3.703493233000 1111180 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": 669829, "vin": [ { "gen": { "height": 669819 } } ], "vout": [ { "amount": 3703493233, "target": { "key": "a5c7a283fc5ccbc5f4d501a705c99e5bc762273e1c1f84ab4d70a9a8e0dc54e8" } } ], "extra": [ 1, 14, 233, 33, 37, 121, 106, 116, 70, 117, 124, 137, 33, 163, 187, 156, 113, 91, 159, 220, 52, 229, 59, 51, 47, 221, 12, 138, 149, 208, 229, 50, 118, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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