Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e4a372cab2f96e8eb15d64c114c9936630d8e3062c7d296ae03dea40004a28f

Tx prefix hash: 088309111ffd98078d2433ecb72af3fb927cd8103cd5a5a6261937db9604425d
Tx public key: adaaff27bfc6c90a6c0d37a43ef0e4fa22424e60c5c6d572d3dc6779c742dbe3
Timestamp: 1709346094 Timestamp [UCT]: 2024-03-02 02:21:34 Age [y:d:h:m:s]: 01:035:19:24:32
Block: 969235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286581 RingCT/type: yes/0
Extra: 01adaaff27bfc6c90a6c0d37a43ef0e4fa22424e60c5c6d572d3dc6779c742dbe30211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efed2272ec962174163345f223f3ccd935d6b7feb9caf556d206fd8c1f270c17 0.600000000000 1429064 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": 969245, "vin": [ { "gen": { "height": 969235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efed2272ec962174163345f223f3ccd935d6b7feb9caf556d206fd8c1f270c17" } } ], "extra": [ 1, 173, 170, 255, 39, 191, 198, 201, 10, 108, 13, 55, 164, 62, 240, 228, 250, 34, 66, 78, 96, 197, 198, 213, 114, 211, 220, 103, 121, 199, 66, 219, 227, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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