Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7df0f81d7ab098cb31953b248fc6daec85f55445ec8b7d7a639dd7e64b312cc4

Tx prefix hash: e2e02d11dd39ad999c4c79f8784dc0bbd23eaaf998bb2f123bb8f09f1d9cfb88
Tx public key: 42b25cd7713c27cc9f075cd7270d80f8630ee219f7bea5f6aeed29e3dd5aee49
Timestamp: 1733764142 Timestamp [UCT]: 2024-12-09 17:09:02 Age [y:d:h:m:s]: 00:130:14:43:33
Block: 1171567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93150 RingCT/type: yes/0
Extra: 0142b25cd7713c27cc9f075cd7270d80f8630ee219f7bea5f6aeed29e3dd5aee49021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f45471b724c72266f48b26b0b18da3fef4fd173b8aaeed0681539961041b76bd 0.600000000000 1657342 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": 1171577, "vin": [ { "gen": { "height": 1171567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f45471b724c72266f48b26b0b18da3fef4fd173b8aaeed0681539961041b76bd" } } ], "extra": [ 1, 66, 178, 92, 215, 113, 60, 39, 204, 159, 7, 92, 215, 39, 13, 128, 248, 99, 14, 226, 25, 247, 190, 165, 246, 174, 237, 41, 227, 221, 90, 238, 73, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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