Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ad695e9e4f308100eeef66dbbb7e5079ee25c9da09e51b74aa3e66cd40e7bbc

Tx prefix hash: 838123d24c1792700dcc52c09c6c5f0f542c0e95809dc619723abccf2b69ea3a
Tx public key: 16353a9d4b3afdec4efe234a54fd4ec23cada47a5d70e595e1d0fc610b25453a
Timestamp: 1735805589 Timestamp [UCT]: 2025-01-02 08:13:09 Age [y:d:h:m:s]: 00:171:20:55:31
Block: 1188465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122452 RingCT/type: yes/0
Extra: 0116353a9d4b3afdec4efe234a54fd4ec23cada47a5d70e595e1d0fc610b25453a021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a9be9140d36cad9b63213e90d22f078feea277927203663139b45bfb39d981d 0.600000000000 1674966 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": 1188475, "vin": [ { "gen": { "height": 1188465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a9be9140d36cad9b63213e90d22f078feea277927203663139b45bfb39d981d" } } ], "extra": [ 1, 22, 53, 58, 157, 75, 58, 253, 236, 78, 254, 35, 74, 84, 253, 78, 194, 60, 173, 164, 122, 93, 112, 229, 149, 225, 208, 252, 97, 11, 37, 69, 58, 2, 17, 0, 0, 0, 7, 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