Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c38fb354ee487b234ac509deea53a5deebfd06e735ae1f96d7dd975d79e92aab

Tx prefix hash: f239f9468611790be2b7a3b7fad0a89d4d65d4c71e493d486c691b2f6fca5d6e
Tx public key: e4e739eef43d2ed36fbd7638250bd9c0782d208ad416c61fc53452a1de9072ae
Timestamp: 1709370669 Timestamp [UCT]: 2024-03-02 09:11:09 Age [y:d:h:m:s]: 01:032:09:11:08
Block: 969436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284136 RingCT/type: yes/0
Extra: 01e4e739eef43d2ed36fbd7638250bd9c0782d208ad416c61fc53452a1de9072ae02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7fa354a400c4de478de0906bb2665a4a953a88b6ee0208449fdc52a89329b26 0.600000000000 1429267 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": 969446, "vin": [ { "gen": { "height": 969436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7fa354a400c4de478de0906bb2665a4a953a88b6ee0208449fdc52a89329b26" } } ], "extra": [ 1, 228, 231, 57, 238, 244, 61, 46, 211, 111, 189, 118, 56, 37, 11, 217, 192, 120, 45, 32, 138, 212, 22, 198, 31, 197, 52, 82, 161, 222, 144, 114, 174, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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