Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cce0b750a630f76579967a3b8b80259e67cca9f767d8c415a1dae3232c998d2

Tx prefix hash: 346783f62557921aff45488dcfee4b8d6846ae9db5df25ede76ca0df8f459dba
Tx public key: e7f6852c6eaf46286fb7f6b795abb4d953d812b6e4353f6c0cf020b76e158277
Timestamp: 1735838645 Timestamp [UCT]: 2025-01-02 17:24:05 Age [y:d:h:m:s]: 00:322:03:08:58
Block: 1188732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227739 RingCT/type: yes/0
Extra: 01e7f6852c6eaf46286fb7f6b795abb4d953d812b6e4353f6c0cf020b76e1582770211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76bfd15e7a31c6f199915911c72fa31a991d20942ccf021f324f3cc26470e3a9 0.600000000000 1675235 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": 1188742, "vin": [ { "gen": { "height": 1188732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76bfd15e7a31c6f199915911c72fa31a991d20942ccf021f324f3cc26470e3a9" } } ], "extra": [ 1, 231, 246, 133, 44, 110, 175, 70, 40, 111, 183, 246, 183, 149, 171, 180, 217, 83, 216, 18, 182, 228, 53, 63, 108, 12, 240, 32, 183, 110, 21, 130, 119, 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