Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8495c0146b8eebf16f4c6e1f3635e39d2f5ca0e6e4d7e53b1345cae8f867d63

Tx prefix hash: eb4f8f606e3c49bb5048b7e884881af2f61b1bfccd2d85346fa5ae577859c427
Tx public key: 787879ff146c9b87b93385e0d5032e93d8b7ec5d1ec5abfb7ff7f9378821dccb
Timestamp: 1735370645 Timestamp [UCT]: 2024-12-28 07:24:05 Age [y:d:h:m:s]: 00:327:17:57:40
Block: 1184865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231745 RingCT/type: yes/0
Extra: 01787879ff146c9b87b93385e0d5032e93d8b7ec5d1ec5abfb7ff7f9378821dccb0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 464c3c58b0343c5c3dceb363137fe801a97a5d7ffc23bf4fcfec2029c4ed3a8c 0.600000000000 1671324 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": 1184875, "vin": [ { "gen": { "height": 1184865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "464c3c58b0343c5c3dceb363137fe801a97a5d7ffc23bf4fcfec2029c4ed3a8c" } } ], "extra": [ 1, 120, 120, 121, 255, 20, 108, 155, 135, 185, 51, 133, 224, 213, 3, 46, 147, 216, 183, 236, 93, 30, 197, 171, 251, 127, 247, 249, 55, 136, 33, 220, 203, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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